Issue
Contribution records
Contributors

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

Give credit to everyone
coaston
avpaderno volunteering
anneke_vde organization(s): iO
greggmarshall volunteering organization(s): Vendor-Tech, Inc. customer(s): ZenSource
rodrigoaguilera customer(s): SystemSeed
anybody volunteering organization(s): DROWL.de
interdruper
jrochate
neclimdul volunteering organization(s): APQC
grevil organization(s): DROWL.de
ikeigenwijs
seanb organization(s): iO customer(s): Erasmus University Rotterdam
ilfelice
drupalninja99 organization(s): Current
dewancodes
xeiro volunteering
steveoriol
daletrexel volunteering organization(s): University of Minnesota
javier_rey
batkor
paul.kim organization(s): Technocrat
g.rocchini organization(s): SparkFabrik
bogdan.dinu volunteering organization(s): United Nations
norman.lol organization(s): 1xINTERNET
Git commit message
Commit types
  • 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

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.