Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
ekl1773 volunteering
tatarbj organization(s): Petend
joelpittet volunteering organization(s): The University of British Columbia
volkswagenchick organization(s): Kanopi Studios
dinarcon organization(s): Agaric
th_tushar volunteering
gobinathm organization(s): TATA Consultancy Services customer(s): Johnson & Johnson
redzeuf organization(s): Happy Coding
sastha volunteering organization(s): TATA Consultancy Services customer(s): Johnson & Johnson
jerdavis organization(s): Horizontal
greggmarshall
thejimbirch organization(s): Kanopi Studios
rachel_norfolk organization(s): Drupal Association
sparklingrobots volunteering organization(s): Drupal Diversity & Inclusion, Pantheon
mandarmbhagwat78
bnjmnm organization(s): Acquia
aburrows organization(s): DigiDrop
joshmiller organization(s): Acro Commerce
chrisdarke organization(s): Hook 42 customer(s): Zicasso, Inc.
realityloop volunteering organization(s): Realityloop
Amarshall volunteering
leslieg volunteering
darren oh organization(s): Cognizant Softvision
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.