Issue
Contribution records
Contributors

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

Give credit to everyone
tsvenson
int
wasare
jackbravo
discursives
eagereyes
CSCharabaruk
kemitix
nunof
elgandoz
killua99
Subbo
branana
7wonders
kristoferaberg
garrettrayj
klipnov
mjross
jeffwidman
ceefour
mailking
Zanel
geerlingguy
scito
criscom
tky
jonasdowney
apb1991
retolist
monican
Satri
ktleow
erdembey
carusen
maxperience
vb
ibex
nelslynn
neurojavi
JJSON
dantz
ajaysolutions
murz
Krusnik02
minnur
hansfn
lameei
intropedro
margokw
deekayen
jordan8037310
lsolesen
anniegreens
eranks
hongpong
juc1
marvil07
dave reid
v.zhakov
vadim s. sabinich
yuriy.babenko
shane birley
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.