Contribution records
Contributors

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

Give credit to everyone
chazz chazz
tharrison tharrison
dutchie76 dutchie76
scotthoff scotthoff
doublejosh doublejosh
bkalbs bkalber
LuckyBamboo LuckyBamboo
RichieRich RichieRich
vincenzo vincenzo
dunklea dunklea
serbanghita serbanghita
JThan JThan
mattcasey mbcasey
Rameez Rameez
0xC0FF33 0xC0FF33
akoymakoydpl akoymakoydpl
venusrising venusrising
volocuga volocuga
laProbeta laProbeta
Mario2 Mario2
Exploratus Exploratus
hedac hedac
pwilson pwilson
marcano Vro
jeffryartavia jeffryartavia
designotb designotb
mja mja
ryanoreilly ryanoreilly
dillonkin dillonkin
broncomania broncomania
held69 held69
mcpuddin mcpuddin
damienmckenna damienmckenna
Gham Gham
alex dicianu dicix
nestor.mata nestormata
m.stenta mstenta
Clément Cleement
Gemini Lights Gemini_Lights
R.Hendel RalfHendel
arun ak ARUN
skiff skiff
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.