Contribution records
Contributors

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

Give credit to everyone
yannickoo yannickoo
caktux caktux
2faroffroad 2faroffroad
Infinitee Inifnitee
dawehner dereine
dianacastillo dianacastillo
pierrozone pierrozone
presleyd presleyd
Geijutsuka Geijutsuka
DanZ DanZ
roderik roderik
joefry Joefry
millionleaves millionleaves
kap316 kap316
wxman wxman
mdvannoort mdvannoort
Leeteq Leeteq
fonant Fonant
marty2081 marty2081
mikeinvaldosta mikeinvaldosta
mxh hauptm
1mundus 1mundus
kamenrs kamenrs
Johnxystus Johnxystus
zzlalani zzlalani
chewie Chewie
markabur markabur
jghyde jghyde
liquid06 liquid06
ilfelice jorgemare
abx abx
dimitrisg dimitrisg
gittosj gittosj
rokk rokk
i92guboj i92guboj
jackhutton jackhutton
lyricnz lyricnz
Asgarden Asgarden
Hemptopia Hemptopia
stolzenhain stolzenhain
jessicakoh jessicakoh
wickus wickus
vendyatelier vendyatelier
stephenrobinson SangersDrupalDude
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.