Issue
Contribution records
Contributors

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

Give credit to everyone
ax
NeoChucky
beginner
fgm
breyten
webchick
chx
m3avrck
yktdan
dopry
puregin
danzell
sfarestam
drumm
Fusion_Sushi
webernet
rkerr
dries
drupalok
stevenpatz
DriesK
sun
drupalgirl
rkendall
cburschka
momper
mrgoltra
zilla
Fayna
ztyx
BioALIEN
baronmunchowsen
oc
Susurrus
Leeteq
robloach
mrintegrity
dnewkerk
christefano
bsherwood
r0g
Wolfflow
pasqualle
sethcohn
alexanderpas
Bojhan
catch
yoroy
RockyMontana
David_Rothstein
int
barinder
am22
KSR
lapadapblah
pal4life
Kjartan
moshe weitzman
robin monks
simon rawson
jose reyero
keith.smith
Christefano-oldaccount
gábor hojtsy
Chris Johnson
wim leers
Michael Phipps
dave reid
John Doe
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.