Issue
Contribution records
Contributors

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

Give credit to everyone
bkosborne organization(s): Princeton University
idebr organization(s): iO
lendude organization(s): iO
anneke_vde organization(s): iO
sylus
jamesyao
rajeshreeputra volunteering customer(s): Shivswarajya Inc.
stijnhau
mark_fullmer volunteering organization(s): University of Texas at Austin
mmarler organization(s): University of Texas at Austin
smulvih2 organization(s): Cinder Systems Corp., Health Canada - HPFB
dieterholvoet organization(s): Minsky
matthiaso organization(s): Minsky
stewest
johan den hollander organization(s): Finalist
joseph.olstad
liam morland organization(s): University of Waterloo
martijn de wit organization(s): Ablerz
stefanos.petrakis volunteering
moshe weitzman
richard.thomas
solideogloria
chewi3
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.