Issue
Contribution records
Contributors

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

Give credit to everyone
fatcrobat
franzkewd
klonos
jmlavarenne
LateNightDesigner
thulstrup
AlexisWilke
bonobo
beckyjohnson
jacobroufa
shadysamir
marcp
AdrianB
attheshow
kendouglass
agileware
mrfelton
graytoby
Trinorae
jthomasbailey
btully
dan_metille
balsagoth
pvasili
phyadmin
kenorb
emattias
ipwa
alexweber
ohnobinki
achton
scorchio
jvieille
leksat
izmeez
keesee
j0rd
chadmkidner
paulgemini
MrMaksimize
kevinob11
aidanlis
semantric
EvanDonovan
lanzs
CZ
robloach
squarecandy
vorapoap
Rosamunda
krisrobinson
rjbrown99
psegarel
brandenlhamilton
gateway69
bdlangton
ispboy
OnkelTem
chilic
digi24
damienmckenna
milovan
markhalliwell organization(s): Tag1 Consulting, Inc.
XiaN Vizjereij
eric.chenchao
man-1982
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.