Issue
Contribution records
Contributors

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

Give credit to everyone
mrcharles
007pig
rp7
albert9000
entilza72
bluesherpa
stefan81
kpojeta
adamwhite
Steven_F
modulist
sunchaser
capellic
rooby
js
lukebrooker
scotwith1t
tahiticlic
drew29
spyderpie
nags338228
pdrake
bramface
ymeiner
aerozeppelin
aitala
doublejosh
ChrisValentine
apoc1
loze
podarok
alan d.
it-cru
danny englander
alexbk66-
anawillem
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.