Contribution records
Contributors

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

Give credit to everyone
amoebanath amoebanath organization(s): ComputerMinds
hudri hudri
joekers joekers volunteering organization(s): Zoocha
rensingh99 rensingh99 organization(s): Red Crackle
xjm xjm organization(s): Acquia
andyf andy organization(s): Fabb
baysaa Baysaa volunteering organization(s): Fabb customer(s): Gizra
alexpott alexpott organization(s): Acro Commerce, Thunder
nod_ nod_ organization(s): Acquia, Smile
lauriii lauriii organization(s): Acquia
andrewmacpherson andrewmacpherson volunteering
tanubansal tanubansal organization(s): Salsa Digital
samiullah samiullah organization(s): Salsa Digital
carroll_webprog ldwyerG volunteering
codebymikey codebymikey organization(s): Zodiac Media
vikashsoni vikashsoni volunteering organization(s): Zyxware Technologies
eelkeblok eelkeblok organization(s): iO
grndlvl grndlvl organization(s): Zivtech
luisrhaas luisrhaas organization(s): CI&T
quietone quietone organization(s): PreviousNext
pankaj.singh pankaj.singh volunteering organization(s): Material customer(s): Drupal India Association
shabana.navas ShabanaBlackborder
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.