Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
ovidenov
quietone organization(s): PreviousNext
rop
mkindred
lendude volunteering organization(s): iO
besek
turneight volunteering
crutch
dqd volunteering organization(s): MAROQQO studios
2pha
monaw
johnpitcairn
guillaumeduveau
yonailo
smustgrave organization(s): Mobomo
alfthecat
loze
gaddman
xavier.masson
binoli lalani organization(s): QED42 customer(s): Drupal India Association
joshua1234511 volunteering organization(s): Salsa Digital
sagarsingh24 organization(s): Unikove Technologies
bramdriesen volunteering organization(s): Sopra Steria
mortona2k
joelpittet organization(s): The University of British Columbia
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.