Issue
Contribution records
Contributors

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

Give credit to everyone
Torenware
maykbrito
mattyoung
higherform
jpetso
starbow
HelloStephanie
Kisama
zmo
steppek
gdd
robbiethegeek
jastylr
jnvsor
fletch11
markabur
karens
DjebbZ
cpill
aaustin
ultimateboy
chadd
mikeybusiness
Aldus
Adeon
hackwater
alpapan
Macronomicus
andrew_hoffi
arlinsandbulte
stevenaburton
scip
yurtboy
kranicservin
LSU_JBob
danny_joris
milehighlife
francesca79
Jackinloadup
nevosa
YK85
jlockhart
goose2000
vict116
ayalon
Bevan
mwbyrd
hermes_costell
mroswell
riverc
mathankumarc
xtfer
vglocus
Budrick
whop
vijaycs85
gábor hojtsy
pam.pkrweb@gmail.com
greg.harvey
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.