Issue
Contribution records
Contributors

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

Give credit to everyone
principessaDS
aaron
MTecknology
pfaocle
Morn
chasz
nedosa
miiimooo
bshensky
weldong
ivrh
duntuk
Shiny
marcingy
domesticat
mradcliffe
Toddv
Fr0s7
kelvinwong
socialnicheguru
Nick_h
adam_b
Equ
srjosh
liliplanet
momper
esplinter
eileenmcnaughton
mgifford
cka3o4h1k
barm
chrism2671
dikovina
somebodysysop
emdalton
hchall
niek_kloots
doughold
TRex2003
Rob_Feature
mauryg
juanjo_vlc
fnikola
daigorocub
snipe
cparrish817
narovi
crystaldawn
niccottrell
thomas23@drupal.org
killes@www.drop.org
fasdalf@fasdalf.ru
thierry.beeckmans
drupal centric
agoel@axelerant.com
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.