Issue
Contribution records
Contributors

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

Give credit to everyone
alberto56 organization(s): Dcycle
lpeabody
dieuwe organization(s): Sparks Interactive
keboca
davo20019
fredonia_webteam
flodevelop
lisp
vistree
sic
juampynr organization(s): Lullabot customer(s): NBCUniversal
pratik_kamble organization(s): QED42
dorficus volunteering
gsa
jimkeller
Lal_ volunteering organization(s): QED42
nironan
dioni organization(s): Code Enigma
tmwagner
attisan
mkindred
steinmb volunteering
adriancotter organization(s): Sierra Club
anybody organization(s): DROWL.de
dieterholvoet organization(s): Minsky
damienmckenna organization(s): Current
berdir organization(s): MD Systems GmbH
jtwalters organization(s): Tableau
firewaller
liam morland volunteering organization(s): OpenPlus, Scouting Waterloo Region
anup.singh volunteering
rupertj organization(s): Chicken customer(s): LocalGov Drupal
drupov
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.