Contribution records
Draft
Contributors

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

Give credit to everyone
yaoweizhen yaoweizhen
markdia markdia
Mike_Waters Mike_Waters
ajayg ajayg
JirkaRybka JirkaRybka
mandclu mandclu
nquocbao nquocbao
vertazzar vertazzar
joshk joshk
fred0 fred0
fizk fizk
blackdog blackdog
noorsaid noorsaid
MantasK MantasK
slantview slantview
iamer iamer
toemaz toemaz
q0rban q0rban
farshid farshid
RAFA3L RAFA3L
andypost andypost
EvanDonovan evandonovan
dinis Dinis
RikiB RikiB
miro_dietiker mirodietiker
cerup cerup
srobert72 srobert72
azinck azinck
alfthecat AlfTheCat
tntclaus tntclaus
AndyW divisivecottonwood
idflorin idflorin
janusman janusman
verta verta
TripleEmcoder TripleEmcoder
sugiggs sugiggs
newmediaist newmediaist
socialnicheguru SocialNicheGuru
omerida omerida
cgmonroe cgmonroe
AlexisWilke alexiswilke
toemaz-gdo toemaz-gdo
Carl Johan cal
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.