Issue
Contribution records
Contributors

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

Give credit to everyone
jensimmons
jacine
catch
aaron
dries
robloach
drupaltronic
jix_
niklp
webchick
cweagans
mcrittenden
eaton
aspilicious
gusaus
naheemsays
boobaa
spencerwyatt
akahn
emmajane
mfer
ipwa
kika
joachim
cliff
marcvangend
rickvug
dixon_
adrinux
michaelverdi
eigentor
reglogge
carlos8f
kiphaas7
yoroy
brightbold
janusman
chandrabhan
citronica
ChrisBryant
BettyJJ
tstoeckler
dodorama
katiebot
flickerfly
johnalbin
seutje
cbovard
andypost
stephthegeek
yched
chx
jide
willmoy
dcrocks
q0rban
mgifford
inlikealion
dmitrig01
EvanDonovan
aac
bleen
mikeloyst
tsi
rfay
thinkinkless
damienmckenna
trevortwining
ericduran
tlattimore
hefox
bojanz
mlncn
borgenk
tsvenson
sun
wretched sinner - saved by grace
dave reid
laura s
manuel garcia
moshe weitzman
jarek foksa
Jeff Burnz
Steven Merrill
Everett Zufelt
david strauss
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.