Contribution records
Contributors

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

Give credit to everyone
rfay rfay
bago bago
rszrama rszrama
vladimiraus VladimirAus
BD3 BD3
acb acb
chefnelone chefnelone
micnap micnap
Als Als
drugan drugan
xrampage16 xrampage16
discipolo discipolo
sundersingh bbergen
vaccinemedia vaccinemedia
cornelyus cornelyus
funkeyrandy funkeyrandy
quercus020 quercus020
mtrax mtrax
iwant2fly iwant2fly
anybody Anybody volunteering
hkovacs hkovacs volunteering
rp7 rp7
mikechr mikechr organization(s): Tabs & Spaces
buerorezo buerorezo
sjmobley sjmobley organization(s): Centarro
ckng ckng organization(s): O8
lnittoli lnittoli
a.ross a.ross
Marko B MarkoBx
xaris.tsimpouris xaristsimpouris
jsacksick jsacksick organization(s): Centarro
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.