Contribution records
Draft
Contributors

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

Give credit to everyone
lvthunder lvthunder
jawi jawi
STINGER_LP STINGER_LP
ab977 ab977
Fohsap Fohsap
majortom majortom
laomiao laomiao
Fannon Fannon
Spacio Spacio
miaoulafrite miaoulafrite
phaidon63 phaidon63
petergus petergus
lachralle lachralle
alienseer23 alienseer23
ClearXS ClearXS
etdouglas etdouglas
Vandalf Vandalf
mgranoski mgranoski
crifi crifi
BigMike BigMike
alforddm alforddm
MilOrg MilOrg
Snarltoof rimbeaux
delibob delibob
teoverton teoverton
calumet calumet
ckleiman ckleiman
chintan4u chintan4u
philiphart philiphart
skomorokh skomorokh
locual locual
thumb thumb
halftone halftone
Dr_Spock Dr_Spock
GovLk GovLk
digitaldonkey digitaldonkey
suneelkushwaha suneelkushwaha
heirecka heirecka
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.