Contribution records
Contributors

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

Give credit to everyone
weboide weboide
grossmann grossmann
guile2912 guile2912
Volx Volx
catch catch
paolomainardi paolomainardi
andyceo andyceo
scottrigby scottrigby
chx chx
ZenDoodles ZenDoodles
jbrown jbrown
sun sun
mjgruta mjgruta
webchick webchick
vijaycs85 vijaycs85
plach plach
dman dman
David_Rothstein drothstein
slashrsm slashrsm
wesleydv wesleydv
jphelan jtphelan
mile23 Mile23 volunteering
cutesquirrel cutesquirrel
pcambra pcambra organization(s): Cambrico
izmeez izmeez
fabianx Fabianx volunteering
georob georob
tim.plunkett tim.plunkett
ñull com2
stefan.r stefan.r
joseph.olstad joseph.olstad
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.