Issue
Contribution records
Contributors

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

Give credit to everyone
not_Dries_Buytaert
browlands
osopolar
Aerodynamo
butler360
jorap
houen
pnigro
crea
Yorgg
vkr11
peterjmag
bcobin
jbrauer
SeanBannister
tkntvdotcom
j0rd
escoles
nanoprobe
leehquk
sangus
cimo
nirad
kalilo
AdrianB
stacysimpson
hlykos
Armyofbobs
srobert72
brulain
espirates
csilfverduk
modctek
gooddesignusa
sapiusenator
leifh
norio
montag
badzilla
bryancasler
stijnbe
liquidcms
vinmassaro
iaminawe
Ron_WI
Krogenar
webengr
bleen
serkan_isin
mrgoltra
jan_v
ingacosta
NickAT
antonisar
drupert55
dealancer
ClearXS
Isostar
nicktr
opal_froot
zet
jackhutton
Tino
tkakanowski
foxman333
barneylodge
sonicthoughts
areafix
lfreitas
mcurry
jrotondo
calefilm
guvser
thoughtcat
candelas
tcibah
rmiddle
dready2011
juc1
dc_marc
mattew
dave reid
drupaloo-1
vincent sg
Alan.Guggenheim
Jerome F
Cynthia Ewer
Todd Young
stewart.adam
eddie.porter
kip stanning
Desi Raaj
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.