Contribution records
Contributors

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

Give credit to everyone
AlexisWilke alexiswilke
binford2k binford2k
bigdave bigdave
mhaudenschild mhaudenschild
WorldFallz worldfallz
thomasvdv thomasvdv
mo6 mo6
stclaird stclaird
xenyo xenyo
dooug dooug
SanDiego SanDiego
shadowmihai shadowmihai
mrsinguyen mrsinguyen
dwhutton dwhutton
bensnyder bensnyder
silurius silurius
webankit babbar.ankit
JohnnyX JohnnyX
tobias tobiaseigen
DnaX DnaX
marcoka eanima
chapatt chapatt
dwalker51 dwalker51
mdm mdm
fpahl fpahl
larowlan larowlan
Vc Developer Vc_Developer
aren cambre arencambre
d.olaresko d.olaresko
Jean Gionet JeanGionet
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.