Issue
Contribution records
Contributors

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

Give credit to everyone
rjacobs
nedjo
tema
xjm
FreddieK
mikgreen
agileware
davepoon
lelizondo
jyg
scottrigby
kmajzlik
adraskoy
real_ate
valderama
justindodge
summit
kevinob11
sachbearbeiter
obrienmd
yareckon
neofactor
brunorios1
pontus_nilsson
rumble
vegardjo
danepowell
askibinski
dellis
fearlsgroove
mgifford
mstrelan
c4rl
hlopes
lahode
pacome
tahiticlic
mzwyssig
genjohnson
jibus
osopolar
robertstaddon
deciphered
rp7
milesw
Sk8erPeter
stred
Countzero
altrugon
drupal_was_my_past
Arnion
sagannotcarl
merilainen
finedesign
keesje
jhodgdon
karsa
jonmcl
froboy
djschoone
colan
tommyk
jcfiala
mxt
Wesgro
mark trapp
Bußmeyer
milos.kroulik
zach.bimson
Jason Dean
arturs.smirnovs
joey-santiago
star-szr
Pete B
Angry Dan
tomb-2
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.