Issue
Contribution records
Contributors

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

Give credit to everyone
HasseMan
sun
rconstantine
escoles
hadsie
drupalninja99
adeb
hnln
willieseabrook
kndr
ksenzee
twod
avner
mcarbone
emilyf
szantog
3dloco
ayalon
gooddesignusa
tallsimon
mrwhizkid
Encarte
NPC
yugongtian
lightstring
ailgm
andyf
justmagicmaria
tchopshop
bforchhammer
chichilatte
esbite
drupa11y
mpotter
gaele
David_Rothstein
anou
mstef
dkingofpa
sassafrass
stevenovy
loze
greggmarshall
samerali
zhangtaihao
vegardjo
prinds
brettbirschbach
Grayside
pedrosp
mstrelan
WorldFallz
shaundychko
juliusvaart
czigor
jenlampton
broeker
bneil
hwasem
rjacobs
vacilando
pianomansam
steinmb volunteering organization(s): University Of Bergen
my-family
danny englander
dave reid
scott.whittaker
Mark Vincent Verallo
Jason Dean
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.