Issue
Contribution records
Contributors

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

Give credit to everyone
yannickoo
transmitter
soul_discharge
sgabe
jcisio
klonos
bluecafe
mcarrera
gpk
robloach
davyvdb
OutOfCtrl
brisbanett
keiths281
Raytracer
frednwright
thegeekunleashed
AdrianB
sk33lz
b3liev3
peezy
bryancasler
phunster
alexandreracine
YK85
mhm
syturvy
kribby
gilcpd
guigui_nyc
chawl
mkrkarthi
mdlueck
yanyan729
Claari
j0nathan
francewhoa
gpascucci
Synthmax
Jetson
amclin
yareckon
clau_bolson
visualnotion
daltonparsons
simoncritchell
Tran
tuwebo
momper
dargente
jackhutton
nattyweb
schasoli
linuxpimp
tanvirahmad
bourgeoy
digibrill
dkl4
dave reid
jozo.starosta
gábor hojtsy
Gabriel R.
d.grechishkin
Marc Bijl
KirstenLangholz
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.