Contribution records
Contributors

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

Give credit to everyone
wayland76 wayland76
jdblank jdblank
Lowell Lowell
jparets jparets
gyver gyver
dogboy72 dogboy72
trofimchouk trofimchouk
davedelong davedelong
mroswell mroswell
hunvreus hunvreus
svihel svihel
hunthunthunt hunthunthunt
josoal josoal
Jehf Jehf
zmove zmove
timpolino timpolino
makara makara
plach plach
momper momper
epikur79 epikur79
scottrigby scottrigby
richardhkirkando richardhkirkando
WorldFallz worldfallz
libeco libeco
wuf31 wuf31
artis artis
aren cambre arencambre
ar-jan ar-jan
moshe weitzman weitzman
darren oh darrenoh
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.