Contribution records
Contributors

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

Give credit to everyone
jriedel jriedel
jmai jmai
fletch11 fletch11
jdm843 JDM843
keyone keyone
socialnicheguru SocialNicheGuru
pathfinderelite pathfinderelite
dustonio dustonio
rootwork rootwork
FoolsRun FoolsRun
karens karens
bdragon bdragon
skyredwang skyred
davea davea
drizzi drizzi
aaronbauman aaronbauman
seanr seanr
yesct YesCT
Macronomicus macrocosm
dhartman dhartman
sandino sandino
bomarmonk bomarmonk
matt v. mattv
woodhous@email.unc.edu woodhous@email.unc.edu
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.