Contribution records
Contributors

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

Give credit to everyone
sylus sylus
kaidjohnson kaidjohnson
ph08n1x ph08n1x
briand44 briand44
damienmckenna damienmckenna
aaron aaron
micbar micbar
SandraVdv sandravdv
jwilson3 jwilson3
peacog Peacog
kaare kaare
ParisLiakos rootatwc
johnennew johnennew
dsnopek dsnopek
twod twod
bkosborne bkosborne
tanc tanc
heddn lucashedding
mgifford mgifford
osopolar osopolar
justanothermark justanothermark organization(s): CTI Digital
drasgardian drasgardian
chrisgross chrisgross
dddbbb danbohea
rwohleb rwohleb
thtas thtas
vistree vistree
rooby rooby
vzblk denis-shishkov volunteering organization(s): EPAM customer(s): Johnson & Johnson
devin carlson DevinCarlson
ec-mdecker ec-mdecker
joseph.olstad joseph.olstad
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.