Contribution records
Contributors

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

Give credit to everyone
jsacksick jsacksick
serg2 serg2
rumblewand rumblewand
cllamas cllamas
GDrupal GDrupal
tnfno tnfno
jacqueschoquette jacqueschoquette
tremix tremix
holeepassion holeepassion
hosais hosais
zeta1600 zeta1600
krisp1 krisp1
JC0nde JC0nde
caco13 caco13
gfury gfury
ressa ressa
randomyao22 timyao1977
manish_tapadar manish_novatree
scott859 scott859
armyofda12mnkeys armyofda12mnkeys
selinav selinav
Jennyu BlueWebNodes volunteering
sergiu.popa sergiu.popa
mark@redhorseinteractive.com mark-at-redhorseinteractive.com
Drupal Bros DrupalBros
Lars Bo Jensen LarsBoJensen
arthur.hylton arthur.hylton
sja1 sja1
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.