Contribution records
Contributors

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

Give credit to everyone
dawehner dereine
larowlan larowlan
davidwbarratt davidwbarratt organization(s): Golf Channel
mile23 Mile23
jhedstrom jhedstrom
Crell Crell organization(s): Palantir.net
fabianx Fabianx volunteering
xjm xjm
alexpott alexpott organization(s): Chapter Three (acquired by Kanopi Studios)
naveenvalecha naveenvalecha volunteering
hussainweb hussainweb organization(s): Axelerant
tstoeckler tstoeckler volunteering
heykarthikwithu heykarthikwithu volunteering organization(s): Valuebound
aleksip aleksip
fgm fgm organization(s): OSInet
vijaycs85 vijaycs85 volunteering organization(s): TATA Consultancy Services customer(s): Pfizer, Inc.
tim.plunkett tim.plunkett
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.