Contribution records
Contributors

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

Give credit to everyone
fakingfantastic fakingfantastic
forestmars forest
edglazer edglazer
mandreato mandreato
udipl udipl
beatnikdude BeatnikDude
nathaniel Nathaniel
equalser equalser
scothiam scothiam
bobafred bobafred
CopyCatty CopyCatty
dikini dikini
istarion istarion
jack_tux jack_tux
garrettrayj garrettrayj
remco75 remco75
mhamed mhamed
giorgio79 giorgio79
nymo nymo
luukyb luukyb
funkym funkym
skolesnyk skolesnyk
notluap notluap
jakonore jhonore
rollingnet rollingnet
georgedamonkey georgedamonkey
dashohoxha dashohoxha
theullrich theullrich
nvd_ai61 nvd_ai61
Patrick D. Hynes Patrick_D.Hynes
Dave Cohen yogadex2
Caspar Behrendt Caspar_Behrendt
joshua.stout joshua.stout
John Klehm JohnKlehm
Will Igetit Will_Igetit
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.