Contribution records
Contributors

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

Give credit to everyone
rjbrown99 rjbrown99
Remon rgeorgy
spacegoat1701 SpaceGoat1701
michaelfavia michaelfavia
brandont brandont
nicholasthompson njt1982
scito scito
dankobiaka dankobiaka
jibus Jibus
Lythimus Lythimus
trackleft trackleft
patrickroma patrickroma
infines infines
som30ind som30ind
ashwinsh ashwin.shaharkar
maximilianmikus mkc
nigelcunningham NigelCunningham
leahtard leahtard
parkout parkout
smitty smitty
liquidcms liquidcms
ToxaViking ToxaViking
abaier abaier
colepacak colepacak
firewaller firewaller
romansta romansta
ben833 ben833
nicholas.alipaz nicholasalipaz
honza pobořil bobik volunteering
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.