Issue
Contribution records
Contributors

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

Give credit to everyone
nirvanajyothi
magnus
faunapolis
EyeChartBrew
farald
sammys
maryts23
kcmongoose
capellic
tebb
toma
ogi
chasz
bensnyder
scottrigby
gagarine
francewhoa
good_man
illuminaut
adik
root_of_roots
mrfelton
ianchan
upupax
cerber0s
arhak
zmove
break9
Jiou
AgentD
reinholdlange
tallsimon
VeeLin
spydmobile
daneyuleb
that0n3guy
watbe
afly
jlevis
adaven
rmjiv
Kudja
3duardo
andb
stoney
adam_b
bonobo
liliplanet
losionok
yanivnizry
chandubhai
ColoMondoMan
dejamuse
sullyman
AdrianB
SethM
wim leers
Rob T
Hyper-1
marius.s
N.Simpson
Eli Baskin
Jeff Burnz
Ali Imtiaz
henrijs.seso
danial namousi
ThePiano.SG
Coupon Code Swap
Flying Drupalist
Renee S
Radiating Gnome
Daniel A. Beilinson
Mark Theunissen
ari-meetai
Roxpace
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.