Issue
Contribution records
Contributors

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

Give credit to everyone
mh86
fago
westbywest
liquidcms
jfinkel
xrampage16
mishac
hnln
Fidelix
jox
chipie
xcono
johnpitcairn
pegah_m
RedJane
cjoy
will_in_wi
bradjones1
deepchandra84
klonos
rasmusth
muschpusch
super_romeo
neddstark
damontgomery
bobslee
lukus
droath
wjaspers
thoughtcat
rooby
akshita
jide
dufferin
mgoh1
petrovnn
RobW
nitebreed
Mat77
kaizerking
yannickoo
retiredpro
gmclelland
radiobuzzer
fearlsgroove
dwalker51
nitinsa
priapurnama
maxplus
golubovicm
marcoka
shubhangibb
truyenle
vistree
f0ns
hondaman900
tim.plunkett
nils.destoop
charlie-s
pepe roni
george.plescan
gaëlg
Renee S
ian-moran
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.