Issue
Contribution records
Contributors

Granted credits are reviewed by maintainers. Learn more about granting credit.

Give credit to everyone
maximiliam
stevector
David_Rothstein
sun
eclipsegc
andypost organization(s): Skilld
xjm organization(s): Acquia
larowlan
sdboyer
webchick organization(s): Acquia
benjifisher
jibran volunteering
klonos
rainbowarray
joelpittet
chx
andrewko
dawehner volunteering organization(s): Tag1 Consulting, Inc.
eiriksm
mortendk
fabianx volunteering
borisson_ volunteering
lauriii organization(s): Druid
pwolanin volunteering organization(s): Acquia
davidhernandez volunteering
tuutti
lokapujya organization(s): Babson College
xano organization(s): Druid, Triquanta
dsnopek
Bojhan
effulgentsia organization(s): Acquia
lewisnyman organization(s): Mearra (formerly known as Wunder)
berdir organization(s): MD Systems GmbH
longwave
alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
mile23
googletorp volunteering
yoroy volunteering
duaelfr volunteering organization(s): Happyculture
sun.core
gábor hojtsy organization(s): Acquia
Jeff Burnz
tim.plunkett
wim leers volunteering organization(s): Acquia
manuel garcia volunteering
bill richardson volunteering
star-szr volunteering
emma.maria
dave reid
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • task: A planned operational or maintenance change to the codebase

See the format of the Git commit message.

Copy and paste the message in the Merge UI screen or commit message. If needed, improve the title after you paste. The message follows conventional commits format.