Contribution records
Contributors

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

Give credit to everyone
kvoelker kvoelker
boztek boztek
kepford kepford
dmitrig01 dmitrig01
omega8cc omega8cc
deviantintegral deviantintegral
skwashd skwashd
7sudos 7sudos
sublyro sublyro
sfyn sfyn
adrinux adrinux
jonhattan jonhattan
supersteph supersteph
tjodolv tjodolv
Rob_Feature bobchristenson
shrop shrop
erikwebb erikwebb
sobi3ch sobi3ch
ao2 ao2
jonabh yuval.j.benhur
2dareis2do 2dareis2do
j0nathan J0nathan
alar alar
fuzzy76 fuzzy76
jgreidy jgreidy
fenstrat fenstrat
jp.stacey jpstacey
Mad Dash Mad_Dash
aidanlis aidan
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.