Issue
Contribution records
Contributors

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

Give credit to everyone
kidsleep
ecstasy2
Cybso
nravens
Jboo
leenwebb
drewish
ragavendra_bn
firstov
sfdrummer
schedal
snowbbdd
csc4
nestor718
jicidre
joachim
thethanghn
mtpultz
hanoii
wayne247
paljsingh
ndmaque
daveplml
suedehead
byronveale
brisath
Bilmar
botris
cpapaya
limazita
indepUser
5n00py
YK85
spikesagal
Sasuke_cub
samc
monteco
marina_v
eforth
nx7208
Jenechka
delboud
pivica
rikimaru0007
ikeigenwijs
rmmcclay
screener
develcuy
drupal_acc
Rosamunda
riverrat
verta
bensquare
kix
amirtaiar
droshani
karishkn
elan4life
sandrewj
rcaracaus
fetemete
chanse
chaiwei
mrcaos
rubenv-1
Sinan Erdem
ball.in.th
Oleksa-1
math-hew
Andrey Zakharov
ravi shankar karnati
JavierGL
fender-dupe
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.