Issue
Contribution records
Contributors

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

Give credit to everyone
chx
RobRoy
BioALIEN
dmitrig01
ChrisKennedy
kbahey
sun
joshk
dries
catch
jhm
kevinweber
bjaspan
forngren
mikejoconnor
rickvug
pwolanin
mnlund
m3avrck
Jaza
zigma
sinasalek
treksler
andreiashu
funana
bcn
iKillBill2
executex
webchick
berdir
Crell
tic2000
meba
Fohsap
scroogie
EvanDonovan
alfaguru
KingMoore
mrfelton
ClearXS
crea
3dloco
arhak
asPagurus
avpaderno
jonhattan
wim leers
moshe weitzman
gerhard killesreiter
gábor hojtsy
killes@www.drop.org
jose reyero
robin monks
damien tournoud
smk-ka
josh waihi
Flying Drupalist
dyke it
bird-cage
hass
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.