Contribution records
Contributors

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

Give credit to everyone
adsilcott adsilcott
merlinofchaos merlinofchaos
earthcub earthcub
konsumer konsumer
jonbowyer jonbowyer
asimmonds asimmonds
just_an_old_punk just_an_old_punk
masood_mj masood_mj
raimondious raimondious
mitchell mitchell
mcfilms mcfilms
robbertnl robbertnl
netbear netbear
anrikun anrikun
SuperMidget SuperMidget
kwixson kwixson
Draupnir Draupnir
julou julou
Shai Shai
brisath brisath
graper graper
game GAMe
LaurenH LaurenH
kenorb kenorb
SeanBannister seanbannister
neorg neorg
scottprive tzoscott
sparkymark sparkymark
taote taote
mattiasj mattiasj
kla2t kla2t
LiveWire LiveWire
rikki_iki rikki_iki
pelach pelach
hedel hedel
basicmagic.net basicmagic.net
Mike Sances Mike_Sances
Christopher Herberte chrisherberte
dean.p dean.p
steven jones darthsteven
Flying Drupalist Flying_Drupalist
seanr seanr
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.