Issue
Contribution records
Contributors

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

Give credit to everyone
landsman
neclimdul organization(s): APQC
timwood volunteering
franksj
PhilippVerpoort volunteering
bwoods organization(s): R2integrated
alison volunteering
idebr organization(s): ezCompany
singularo volunteering organization(s): iseek computing
hussainweb organization(s): Axelerant
zakiya organization(s): Chapter Three (acquired by Kanopi Studios)
colan organization(s): Colan Schwartz Consulting, Consensus Enterprises
ladybug_3777
hawkeye.twolf organization(s): Kalamuna
nagy.balint organization(s): Agence Inovae
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.