Contribution records
Contributors

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

Give credit to everyone
andypost andypost
mikeytown2 mikeytown2
neilhanvey neilhanvey
movin360 movin360
inno81 inno81
blackandcode blackandcode
drewish drewish
drupalerocant drupalerocant
gerhardbaumeister gerhardbaumeister
Jorrit jorrit
kaizerking kaizerking
ayalon ayalon
mh86 mh86
firfin firfin
merlinofchaos merlinofchaos
maximpodorov maximpodorov
mrfelton mrfelton
eclipsegc eclipsegc
mcfilms mcfilms
damienmckenna damienmckenna
kenorb kenorb
jlapp jlapp
kalabro kalabro
bryancasler animelion
mikeker mikeker
jhedstrom jhedstrom
japerry japerry
magicmyth magicmyth
Exploratus Exploratus
dgwebcreative dg
kristiaanvandeneynde kristiaanvandeneynde
geresy geresy
pfrenssen pfrenssen
osopolar osopolar
dave reid davereid
Adon Irani AtRiskMedia
Kojo Unsui kojo
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.