Contribution records
Contributors

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

Give credit to everyone
danba danba
jeremy Jeremy
conniec conniec
dchaffin dchaffin
Babalu Babalu
equalspeterd equalspeterd
westblad westblad
famousb famousb
jrglasgow jrglasgow
tgcondor tgcondor
fessio fessio
zilla zilla
sersim sersim
aflores3 aflores3
danyg danyg79
NidSquid NidSquid
OneTwoTait OneTwoTait
neochief neochief
superflyman superflyman
WildBill WildBill
ericjam ericjam
StoreV StoreV
MedicSean37 MedicSean37
clo75 clo75
Stef01 Stef01
demo9 demo9
holesovice holesovice
bgadmin bgadmin
Mrzeigler Mrzeigler
moshe weitzman weitzman
manuel garcia manuelgarcia
Frank.Poulsen Frank.Poulsen
Flying Drupalist Flying_Drupalist
todd nienkerk toddnienkerk
dave kopecek DaveKopecek
keith.smith keithsmith
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.