Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
rszrama
dbkern
jantoine
redna
brunorios1
bojanz organization(s): Centarro
Camario39
amfis
reecemarsland
MickL
msmithcti
rfay
joachim
jkthng
deggertsen
JMTorres
dianikol
jazzdrive3
philipz
frost
summit
Donatoo
technikh
jozzhart
carrierawks
ahimsauzi
kiwimind
gynekolog
chanella
dedek
sjs205
edboost
gratefulsk
Isostar
howardhuang
FriedJam
rutan
drupalerocant
phily
immoreel
pixelsweatshop
Kolo
hockey2112
zmove
tararowell
mmcmmc
fahadurrehman
justtoomany
joegl
leendertdb
adriaav
demonde
mennonot
yalasta
hanskuiters
IckZ
zenimagine
jamesrobertson
designate
ljgra
millionleaves volunteering
kevster
Darren Shelley
lyle@4fs
Barto.G
Sinan Erdem
alex.87
mihail.andreev
fox mulder
vlad.dancer organization(s): Drupalway
barnabas.nagy volunteering
dankung1
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.