Issue
Contribution records
Contributors

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

Give credit to everyone
netentropy
shrimphead
TimG1
funkmasterjones
whatdoesitwant
geerlingguy
alex_b
drewish
derekwebb1
dvbii
infojunkie
webdeli
AntiNSA
srobert72
mirzu
adityakg
FreddieK
andrewlevine
twistor
dawehner
summit
meatbag
loliearn
aaron_michels
elliotttf
rbayliss
imclean
roderik
tema
jibberish
joshuabud
atolborg
claar
Taxoman
cmcintosh
uxjam
pyrello
danielb
kirkcaraway
kvyn
jshimota01
stella organization(s): Annertech
dromansab
megachriz volunteering
czigor
b-prod
last call media
bluegeek9 volunteering organization(s): Knowledge Learning Labs, Portland Webworks
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.