Issue
Contribution records
Contributors

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

Give credit to everyone
dergachev
jcwatson11
jwaxman
ak
AppleAp
tarvid
laryn
labrown
3cwebdev
mkjones
sam6
jtjones23
jvinci
joncup
T1TAN23
traviscarden
danielb
geodaniel
dman
mtndan
DanielJohnston
niklp
giorgio79
adam_b
zeezhao
juan_g
cpill
stewsnooze
B747
tomhung
banglogic
robbertnl
jcamfield
cbosner
brip
darrellhq
MidGe48
aquamaureen
sockah
drupaloSa
clivesj
arojoal
portulaca
brainski
petey318
hvalentim
vidmarc
StuartDH
liliplanet
barry_fisher
juicytoo
yanivnizry
timlie
mattheweigand
rikvd
yurtboy
kenorb
acrollet
lbrown
kevinwalsh
doughold
rezboom
kepford
hansrossel
a_c_m
alegacy
latte
blup
Maccers
ckidow
spl13
frank ralf
Coupon Code Swap
Chris Charlton
miro.log
sammy-node
Robrecht Jacques
Road Runner
Gumk-1
daniel.hunt
tanoshimi
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.