Contribution records
Contributors

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

Give credit to everyone
kbentham kbentham
cilefen cilefen
robpowell robpowell volunteering
rob230 Rob230
michael_wojcik michael_wojcik volunteering organization(s): Current customer(s): Commonwealth of Massachusetts
rbayliss rbayliss organization(s): Last Call Media
navneet0693 navneet0693 volunteering organization(s): QED42
rahulrasgon rahulrasgon organization(s): QED42 customer(s): Drupal India Association
chetanbharambe chetan18 organization(s): QED42 customer(s): Drupal India Association
atul4drupal atul4drupal organization(s): Material customer(s): Drupal India Association
smustgrave smustgrave organization(s): Mobomo
glenndw GlennDW volunteering
ryan.ryan ryanissamson organization(s): Current
suresh prabhu parkala SureshPrabhuParkala organization(s): Specbee
jhandsta joris organization(s): Anvil customer(s): VDAB
dcam dcam
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.