Issue
Contribution records
Contributors

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

Give credit to everyone
geerlingguy
tlattimore
bowersox
Bojhan
bleen
donSchoe
aschiwi
dcmouyard
lewisnyman
jurriaanroelofs
mthart
jessebeach
dreamleaf
wfx
jide
hedley
bryancasler
ckng
drupaltronic
idflood
willmoy
tomgf
mcrittenden
aaronpinero
yeti22
chx
drupa11y
tsi
mgifford
dermotholmes
teknikqa
aristeides
paganwinter
cweagans
brewthis
webchick
partyp
kattekrab
couturier
valeratal
Crell
arelem3
sandwalk3r
c4rl
krisDOTco
xjm
cilefen
avpaderno volunteering
longwave organization(s): Full Fat Things
Andy Britton
Jeff Burnz
lars toomre
myles green
Tor Arne Thune
Diane Bryan
laura s
gdzine
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.