Contribution records
Contributors

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

Give credit to everyone
digemall digemall
vm vm
Sera Sera
oriol_e9g oriole9g
berdir berdir
JohannE JohannE
YK85 YK85
marvil07 marvil07
abbasmousavi abbasmousavi
daltonparsons daltonparsons
nancydru nancyw
verta verta
Slovak slovak
Briscoe Briscoe
Stalski stalski
penguintrax penguintrax
scotwith1t phrancescot
puddyglum Puddyglum
Andrew Schulman andrewschulman
john franklin franklin
sbogner@insightcp.com sbogner@insightcp.com
hass hass
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.