Contribution records
Draft
Contributors

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

Give credit to everyone
marcoBauli marcobauli
sun sun
jaypan JayMatwichuk
venkatd venkatd
codevoice thehandyman
jmcerda jmcerda
xurizaemon xurizaemon
Algae_94 Algae_94
mattyoung mattyoung
mthomas mthomas
valderama valderama
mrfelton mrfelton
droplet droplet
nandotinoco nandotinoco
klonos klonos
nevosa nevos
dawehner dereine
fischeme fischeme
catch catch volunteering
RunePhilosof RunePhilosof
cilefen cilefen
jmuzz muzzl
dkre dkre
bkosborne bkosborne organization(s): Princeton University
malcolm_p malcolm_p
damien tournoud damz
mike-michal mike-michal
kkaefer timcn
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.