Issue
Contribution records
Contributors

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

Give credit to everyone
mfer
stella
pcambra
carlitus
j0rd
korvus
nevergone
Leeteq
cmoad
gzfelix
svilen
mikl
matt_paz
katbailey
dropcube
oliverpolden
darvit
kje
lukus
c0m4
xmoe
cardentey
jurriaanroelofs
jcmarco
markus_petrux
dddave
mrfelton
asak
KrisBulman
jordanmagnuson
boobaa
kenorb
lucian303
vivianspencer
logicalpat
jmar777
mark_r
oysstr
quindio
gausarts
marcus7777
iaminawe
klamzo
AdrianB
dquakenbush
jthomasbailey
mdeltito
sobi3ch
zejkee
ericwindham
whatdoesitwant
dtrainor
zilverdistel
stefan81
okeedoak
danbretl
manasiv
srobert72
sreynen
webflo
3dloco
John Resig
Flying Drupalist
aleksey.tk
Renee S
mugginsoft.net
Tom Van Schoor
jan kellermann
bird-cage
dmitriy.trt
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.