Issue
Contribution records
Contributors

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

Give credit to everyone
mcdwayne
rudranil29
WidgetsBurritos organization(s): Rackspace
bircher volunteering organization(s): Nuvole
andreyjan organization(s): JAKALA (formerly FFW)
jeroent organization(s): iO
mikemadison organization(s): Acquia
mandclu organization(s): Northern Commerce
japerry organization(s): Acquia
mrpauldriver
markdorison organization(s): Chromatic
achap
marcvangend volunteering organization(s): ronder
cozydrupalnerd volunteering organization(s): Acquia
hugovk organization(s): Digia customer(s): Yle - Finnish Broadcasting Company
fabsgugu
ejrasmus volunteering
gal magrisso
mr.baileys organization(s): SQLI - Belgium
arijits.drush volunteering
joseph.olstad
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.