Contribution records
Contributors

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

Give credit to everyone
sol1313 sol1313
cogno cogno
pthite pthite
snowmountain snowmountain
osarusan osarusan
LTech LTech
tchurch tchurch
RussLB RussLB
chrsnlsn chrsnlsn
charlesjc charlesjc
storytellerjeff storytellerjeff
sk33lz sk33lz
jduhls jduhls
ditcheva ditcheva
rvb rvb
gukudrupal gukudrupal
xl_cheese xl_cheese
capfive capfive
bburg johnbburg
dwkitchen dwkitchen organization(s): Johnson & Johnson
izmeez izmeez
kevster kevster
astonvictor AstonVictor volunteering organization(s): DevBranch
charlie-s csdco
Johann Wagner johannwagner
muhammad.tanweer muhammad.tanweer
peter.thorndycraft peter-thorndycraft
m.e. m.e.
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.