Issue
Contribution records
Contributors

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

Give credit to everyone
chx
catch
sepeck
Shai
btopro
robloach
mfer
kika
beeradb
dmitrig01
insite2000
beginner
bsherwood
michaek
webchick
George2
rcross
minesota
rickvug
naheemsays
joshmiller
niklp
timmillwood
alex_b
mcrittenden
damienmckenna
q0rban
kevinquillen
eaton
modulist
Crell
adrian
momper
hedac
deekayen
dries
skwashd
kattekrab
knibals
bfroehle
gdd
keith.smith
damien tournoud
dave reid
greg.harvey
boris mann
laura s
Tor Arne Thune
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.