Issue
Contribution records
Contributors

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

Give credit to everyone
flickerfly
designerbrent
DenRaf
gareth_w
coupet
rares
uk105
michelle
darumaki
BluesmanEP
xzelan
Applied_Microeconomics
bonobo
gustav
STNyborg
bijoytm
matteoraggi
ggevalt
dubois
sprugman
surlyrobot
duntuk
andrewbenkard
pillarsdotnet
najibx
JuLearn
ariflukito
itangalo
DanielJohnston
rkeppner
Babalu
nally
jabberw0cky
djbdjb
petey318
g10tto
nonsie
parkej60
liliplanet
marqpdx
3cwebdev
fdelente
erwinwolff
JuliaKM
derjochenmeyer
Dimm
bigjim
Rosamunda
wkmit
concretebox
pablokenfold
dankney
jayburgh
matt2000
juan_g
zlay3r
criptos
earthangelconsulting
kevinquillen
scottbaetz
ytokan
ashokkumarc
mfuggle
gcassie
ezrabutler
gkam
Ultraorganic
emasters
dilvish
Mr. Carpenter
moshe weitzman
robert castelo
jozef.benicky
test_drupal-1
agerson
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.