Issue
Contribution records
Contributors

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

Give credit to everyone
webchick
jessebeach volunteering
Bojhan
effulgentsia
dries
lmdoom
sun
aspilicious
lewisnyman
mallezie
jibran
attiks
nod_
chx
mgifford
kerasai
designfitsu
mradcliffe
yoroy
David_Rothstein
johnalbin
klonos
larowlan
robloach
catch
mikeytown2
seanr
amateescu
andypost
alexpott
shyamala organization(s): UniMity Solutions Pvt Limited
damienmckenna
msonnabaum
eaton
Snugug
rteijeiro
tkoleary organization(s): Acquia
sdboyer
Blooniverse
rainbowarray
pieterdc volunteering organization(s): Randstad Digital customer(s): Government of Flanders
dawehner
tstoeckler
xjm
mcrittenden
joelpittet
wim leers
damien tournoud
gábor hojtsy organization(s): Acquia
dave reid
jl.images
moshe weitzman
laura s
Jeff Burnz
chr.fritsch organization(s): Thunder
seosopt
hass
Git commit message
Commit types
  • 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

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.