Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
jeevanbhushetty organization(s): QED42
piyuesh23 organization(s): QED42
bramdriesen volunteering organization(s): Capgemini, Sopra Steria
lukasss volunteering
xaa volunteering
mrfrankiegio
renrhaf organization(s): CGI customer(s): Ville de Montréal
berenddeboer
tushar1 organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
darksnow customer(s): manifesto
dqd volunteering organization(s): MAROQQO studios
ptgraber
douggreen volunteering
rp7 customer(s): Government of Flanders
chuyenlv organization(s): JAKALA (formerly FFW)
aaronbauman organization(s): Message Agency
orlando.thoeny organization(s): Namics customer(s): Namics
jepster_
vivek panicker organization(s): Innoraft customer(s): Drupal India Association
subhransu sekhar
joachim namyslo
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.