Contribution records
Contributors

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

Give credit to everyone
preventingchaos gcopenhaver
Starbuck Starbuck
lilou lilou
realistknight realistknight
wildtang3nt wildtang3nt
oadaeh oadaeh
optalgin optalgin
creativepragmatic creativepragmatic
intropedro intropedro
sammorgan sammorgan
deadmalc deadmalc
mbull mbull
spydmobile spydmobile
randya randya
rboy rboy
lucacerone lucacerone
dkreviews dkreviews
kgelner kgelner
hafizul hafizul
sotiris sotiris
magnus Magnus
davedelong davedelong
Passionate_Lass Passionate_Lass
modctek modctek
pablokenfold pablokenfold
jhujsak jhujsak
eblues eblues
engelmicha engelmicha
himtuna himtuna
Cyber-Jay Cyber-Jay
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.