Contribution records
Contributors

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

Give credit to everyone
rachel_norfolk rachel_norfolk organization(s): Open Development Ltd customer(s): Horizons Unlimited
pguillard pguillard
balagan balagan
xjm xjm organization(s): Acquia, xjm
Bojhan bojhan volunteering
vikashsoni vikashsoni volunteering organization(s): Zyxware Technologies
ranjith_kumar_k_u ranjith_kumar_k_u volunteering organization(s): Material customer(s): Drupal India Association
alexpott alexpott organization(s): Acro Commerce, Thunder
aaronmchale AaronMcHale
acbramley acbramley organization(s): PreviousNext
asha nair asha_nair organization(s): Zyxware Technologies
Manibharathi E R Manibharathi E R customer(s): Material
Bushra Shaikh Bushra Shaikh organization(s): QED42 customer(s): Drupal India Association
benjifisher benjifisher volunteering organization(s): Harvard Web Publishing
rkoller rkoller
simohell simohell organization(s): Druid
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.