Issue
Contribution records
Contributors

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

Give credit to everyone
tonifisler
ozin volunteering
xem8vfdh
iojonep
jacktonkin organization(s): ISSUP
dawehner organization(s): Chapter Three (acquired by Kanopi Studios)
michielnugter volunteering organization(s): Synetic
arvidkuipers
tedbow organization(s): Acquia
MaskOta
xjm organization(s): Acquia
dpagini volunteering
Mixologic organization(s): Drupal Association
joelpittet organization(s): The University of British Columbia
jofitz organization(s): ComputerMinds
Munavijayalakshmi organization(s): Valuebound
andrewmacpherson volunteering
droplet
kryp71c volunteering
mohit_aghera volunteering organization(s): Axelerant
swetashahi organization(s): Material
una_maria volunteering organization(s): Amazee Labs
zviryatko
alexpott organization(s): Acro Commerce
james.williams organization(s): ComputerMinds
ron collins
trupti bhosale organization(s): Axelerant
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.