Issue
Contribution records
Contributors

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

Give credit to everyone
minoroffense organization(s): Coldfront Labs Inc.
wiktorb
iamsquared
Dentorat
Novascreen
yang_yi_cn
rooby
DaneMacaulay
gooddesignusa
chefnelone
kenorb
alexweber
hkirsman
juliakoelsch
emanaton
jonathan_hunt
damienmckenna
sokrplare
couloir007
ada05
bneil organization(s): The University of Iowa
adam1
jwilson3 organization(s): Bluespark
thronedigital
gvso organization(s): Google Code-In
thegentleman
lbrassaw volunteering
thetwentyseven
justinen
l0calh0rst
randell
Adam S
eduardo.flores
Denis Danielyan
minax.de
maadis.ie
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.