Contribution records
Contributors

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

Give credit to everyone
dmundra dmundra organization(s): CivicActions
bnjmnm bnjmnm organization(s): Acquia
nod_ nod_ volunteering organization(s): Acquia, Eclipse Foundation
finnsky finnsky organization(s): Skilld
andypost andypost volunteering organization(s): Skilld
rikki_iki rikki_iki organization(s): PreviousNext
anchal_gupta Anchal_gupta12 organization(s): Material customer(s): Drupal India Association
quietone quietone organization(s): PreviousNext
mgifford mgifford organization(s): CivicActions
xjm xjm organization(s): Agileana
lauriii lauriii organization(s): Acquia
vladimiraus VladimirAus organization(s): Tomato Elephant Studio
catch catch organization(s): Third and Grove
smustgrave smustgrave organization(s): Mobomo
andy-blum ablum organization(s): Lullabot
wim leers wimleers organization(s): Acquia
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.