Contribution records
Contributors

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

Give credit to everyone
gpeach GPeach
Tara1981 Tara1981
stockliasteroid stockliasteroid
ParisLiakos rootatwc
murz murz
garrettc garrettc
szt szt
lilbebel lilbebel
Abilnet Abilnet
Pisco Pisco
attiks attiks
yvmarques yvmarques
netw3rker netw3rker
viseser viseser
mariagwyn mariagwyn
protoplasm protoplasm
joelrotelli joelrotelli
dustinrwh dustinrwh
Sknight17 Sknight17
mamanerd mamanerd
haqinai haqinai
mile23 Mile23
hbalagtas hbalagtas
bstoppel stoppel
vparfaniuc vparfaniuc
elBradford elBradford
TheBarnacle TheBarnacle
j0rd j0rd
Piyushagr ankit.garg
yannickoo yannickoo
jday janette
selinav selinav
mgifford mgifford
marsdk marsdk
dhallennem dhallennem
igor.ro igorro
damien tournoud damz
baby.hack baby.hack
alan d. aland
NowThatsCookin.Com NowThatsCookin.Com
Sridharan-1 Sridharan-1
finn lewis ecofinn
gaele gaele
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.