Issue
Contribution records
Forks management
Issue edit
Contributors

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

Give credit to everyone
ivavictoria
cilefen volunteering
borisson_ volunteering
Deno
dbielke1986
alexpott
tanubansal organization(s): Salsa Digital
quietone volunteering
ayushmishra206 organization(s): OpenSense Labs
adityasingh volunteering organization(s): Material customer(s): Drupal India Association
xjm organization(s): Acquia
srilakshmier organization(s): Valuebound customer(s): Valuebound
catch organization(s): Third and Grove
perelesnyk organization(s): Digital Pulp customer(s): Rutgers University
smustgrave organization(s): Mobomo
wylbur organization(s): Electric Citizen
fgjohnson@lojoh.ca
raman.b organization(s): OpenSense Labs
rinku jacob 13 organization(s): Zyxware Technologies
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.