Issue
Contribution records
Contributors

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

Give credit to everyone
factoryjoe
chrisada
pancho
SeanBannister
mcurry
psicomante
maartenvg
dugh
ericjam
rfay
bsherwood
geerlingguy
dddave
momper
mean0dspt
3duardo
jgossage
funana
David_Rothstein
jackalope
babbage
Cool_Goose
arnd
bendshead
zzlong
jbc
saccard
degure
MGParisi
reglogge
Duplika
axbom
mkrakowiak
danfinney
kevcol
noovot
morleti
yraffah
jorsol
zooki
iamwhoiam
webchick
cazador
superfly
yoroy
espirates
Aveu
kaakuu
yched
jeffschuler
mlncn
Bojhan
ctmattice1
amc
mcrittenden
cliff
femrich
RKS
xjm
yesct
TallDavid
jhedstrom organization(s): Phase2 customer(s): Memorial Sloan Kettering Cancer Center
acbramley organization(s): PreviousNext
moshe weitzman
David Hull
Gurpartap Singh
thomas23@drupal.org
dave reid
todd nienkerk
Gerald Mengisen
damien tournoud
rob c
Augusto Ellacuriaga
mr.baileys
Everett Zufelt
alan d.
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.