Issue
Contribution records
Contributors

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

Give credit to everyone
danielnolde
yesct
lee20
dharmanerd
bdragon
daneyuleb
kenwen
dynamite
theabacus
lyricnz
1kenthomas
jerry
SilenceEchoed
socialnicheguru
zirafa
kenorb
designwork
jrosen
keva
cedrix
ohira
spyderpie
bjalford
burgs
scottrigby
dionysio
jrglasgow
internets
iThinkWorks
vivianspencer
dzepol
libeco
EvanDonovan
mrtoner
juicytoo
webanalya
andrewsuth
exobuzz
joodas
niles
attiks
tamasco
nathaniel
merzikain
DrupalKing
rfay
drumnjo
nickl
fletch11
kpojeta
resynthesize
solona
roderik
chriscalip
sgallen
summit
nasheet
ankur
Matt Townsend
d.clarke
greg.harvey
glass.dimly
Phil Wolstenholme
jody lynn
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.