Contribution records
Contributors

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

Give credit to everyone
hktang hktang
pfrilling pfrilling volunteering organization(s): Oomph, Inc.
dcam dcam organization(s): USDA-ARS
chrisck chrisck
robertragas robertragas organization(s): Open Social
venu_bhagirath venu_bhagirath
timwood timwood
mialdi98 mialdi98
terry_kolodiy TerryKolodii volunteering organization(s): DevBranch
guedressel guedressel organization(s): Protobyte
steinmb steinmb organization(s): University Of Bergen
gokul.jayan gokul.jayan volunteering organization(s): Power CMS Technology
r.aubin raubin organization(s): Oomph, Inc.
solideogloria solideogloria
jwylarsen jeffwylarsen
danflanagan8 danflanagan8 volunteering
benjifisher benjifisher volunteering organization(s): Harvard Web Publishing
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.