Issue
Contribution records
Contributors

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

Give credit to everyone
gdemet organization(s): Palantir.net
nod_ organization(s): Acquia
anoopjohn organization(s): Zyxware Technologies
fgm organization(s): OSInet
catch organization(s): Third and Grove
rszrama organization(s): Centarro
pcambra organization(s): Cambrico
dreamleaf
quietone organization(s): PreviousNext
rachel_norfolk volunteering
richo_au
darvanen organization(s): Sitback Solutions
volkswagenchick organization(s): Red Hat
ckrina organization(s): Lullabot
dbungard
dinarcon organization(s): UnderstandDrupal.com
froboy organization(s): ImageX
hussainweb organization(s): Axelerant
macjules
markie organization(s): Kanopi Studios
mlhess
ninelivesblackcat volunteering organization(s): Pantheon
ojchris volunteering
ultimike organization(s): DrupalEasy
vonreyes organization(s): Drupal Association
darren oh organization(s): Cognizant Softvision customer(s): Estée Lauder Companies
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.