Contribution records
Contributors

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

Give credit to everyone
mdupont mdupont
larowlan larowlan
jhodgdon jhodgdon
markabur markabur
catch catch
pixelite pixelite
webchick webchick
devenderdagar devenderdagar
derekahmedzai derekahmedzai
khiminrm khiminrm
birdonwire birdonwire
Jo_ Jo
wojtha wojtha
Jevedor Jevedor
dcrocks dcrocks
pingers pingers
404 404
sledan sledan
jeffschuler jeffschuler
m4olivei m4olivei
waltf waltf
marvzz marvzz
bcreeves bcreeves
avpaderno avpaderno
spencerthayer spencerthayer
vitok-dupe vitok-dupe
star-szr star-szr
Bill Pair Bill_Pair
Steven.Pescador SAF13
elijah lynn ElijahLynn
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.