Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
mbaynton organization(s): Pantheon
aaronmchale volunteering
johnwebdev
ressa organization(s): Ardea
mmjvb volunteering
Mixologic organization(s): Drupal Association
mile23 volunteering organization(s): CivicActions
webchick organization(s): Acquia
alexpott organization(s): Acro Commerce, Thunder
geerlingguy organization(s): Midwestern Mac, LLC
nicxvan
tyeth
bserem organization(s): zehnplus
jcandan
lpalgarvio volunteering
leksat organization(s): amazee.io
benjifisher volunteering organization(s): FRUITION
makkus183 volunteering
mchelen
zuhair_ak
crasx volunteering organization(s): Bounteous
smustgrave organization(s): Mobomo
quietone organization(s): PreviousNext
joachim organization(s): Factorial.io
imclean
ultimike organization(s): DrupalEasy
joestewart organization(s): Current
longwave organization(s): Full Fat Things
greg.1.anderson organization(s): Pantheon
brad.bulger
ben coleman organization(s): Accelerated Design, Inc.
james.williams organization(s): ComputerMinds
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.