Issue
Contribution records
Contributors

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

Give credit to everyone
drupalina
neochief
munikho
OneTwoTait
nirad
virtualdrupal
sashken2
evilworm
damienmckenna
dicreat
bacchus101
alanmparry
Sownn
Babalu
scoorch
Gyt
jrpowell01
andypost
simplyManu
Kostyan_Vinnikov
taran2l
zarudnyi
Craftsman
nikemen
ltwinner
hmquien
halfiranian
stephencarr
v8powerage
akongz
gregstout
tevih
CanOne
dimitriz1
gauravkhambhala
flyinghorse
godewebog
ccshannon
chilic
asak
calte
mauritsl
bertboerland
homoludens
ember5000
rjbrown99
akalata
marvix
marcoka
amedjones
blainelang
SewFresh
msathesh
manjeet
grotto
qzmenko volunteering organization(s): DrupalJedi
a.mohax
Flying Drupalist
daniel wentsch
jeno-1
pixelpreview@gmail.com
Jonah Ellison
kip stanning
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.