Issue
Contribution records
Contributors

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

Give credit to everyone
bkosborne organization(s): Princeton University
mikejw organization(s): University of Adelaide
svendecabooter volunteering organization(s): Sven Decabooter customer(s): Torchbox
colan organization(s): Colan Schwartz Consulting
SlayJay
jvandyk
pagolo
istryker
coderdan organization(s): Phase2
kalis1
jozzy_a organization(s): Capgemini customer(s): Care Quality Commission
parasolx organization(s): Hadafi Solution & Resources
joelpittet organization(s): The University of British Columbia
heddn organization(s): MTech, LLC
jrearick organization(s): Iowa State University
kpaxman
jose reyero volunteering
claudiu.cristea volunteering organization(s): Webikon customer(s): European Commission and European Union Institutions, Agencies and Bodies
Git commit message
Commit types

Click on the types below to update the "Commit type" input.

  • 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
  • task: A planned operational or maintenance change to the codebase

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.