Contribution records
Contributors

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

Give credit to everyone
Kjartan kjartan
shane shane
marky marky
cel4145 cel4145
robertdouglass robertDouglass
jonbob JonBob
gtoddv gtoddv
joshuajabbour joshuajabbour
m_freeman2004 m_freeman2004
dr05 dr05
jasonwhat jasonwhat
ezheidtmann clydefrog
kbahey kbahey
djnz djnz
Geary geary
fgm fgm
Crell Crell
dries dries
bexecho rorris
cmsproducer iDonny
brianV brianV
killes@www.drop.org killes
Eric Scouten scouten
ilkay.can Drupella
moshe weitzman weitzman
keto-1 keto-1
Git commit message
Commit types
  • 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

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.