Contribution records
Contributors

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

Give credit to everyone
litwol litwol
chx chx
jeremy Jeremy organization(s): Tag1 Consulting, Inc.
robertdouglass robertDouglass
sylv3st3r sylv3st3r
bblake bblake
ogi ogi
pillarsdotnet pillarsdotnet
catch catch
berdir berdir
hswong3i hswong3i
quicksketch quicksketch
estepix estepix
sinn sinn
ywarnier ywarnier
rogical rogical
wedge wedge
thedavidmeister thedavidmeister
jimyhuang jimyhuang
Firemyst Firemyst
markpavlitski markpavlitski
pwaterz pwaterz
RobKoberg RobKoberg
_-. underscore_dash_dot
jaroslaw.kaminski jaroslaw.kaminski
igor.ro igorro
Git commit message
Commit types
  • 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

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.