Contribution records
Contributors

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

Give credit to everyone
cmarti cmarti
cgoffin cgoffin organization(s): Sopra Steria
lamp5 lamp5
amaisano amaisano
wmike7 wmike7 organization(s): Monarch Digital
alexpott alexpott
bstan bstan organization(s): Liberty Mutual Group
lendude Lendude organization(s): iO
andypost andypost volunteering organization(s): Skilld
kishor_kolekar kishor_kolekar volunteering organization(s): QED42 customer(s): Drupal India Association
acrazyanimal jpayne volunteering
tanubansal tanubansal organization(s): Salsa Digital
elgandoz elgandoz volunteering
catch catch organization(s): Third and Grove
kerasai bmoresafety20
_kash_ _KASH_
joseph.olstad joseph.olstad
raman.b ramanbatra1709 organization(s): OpenSense Labs
krzysztof domański krzysztof_domanski organization(s): abventor
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.