Issue
Contribution records
Contributors

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

Give credit to everyone
dhalbert
dylanb
ceeweb
helmo
jaypan
raulmuroc
protools
jazzper
achton
pierrozone
bsergiu
kevinquillen
donalfitz
pianodavid
basvredeling organization(s): Code Culture
fredklopper
seanbfuller
mobius_time
twooten
torgospizza volunteering
mhamed volunteering
patrickwatzeels
dasginganinja volunteering
dobie_gillis
stolzenhain
delacosta456
deajan volunteering
zakmahboub22 volunteering
pascalli
ragavendra_bn
knalstaaf
mfuller526 volunteering
andraeray volunteering
scott859
TristanTheKnightAway
hanskuiters
pyim volunteering
mikeytown2
davidandaman volunteering
joehudson
joelpittet organization(s): The University of British Columbia
Dru18
fonant
web226
Andru volunteering
bluesky_still
zorz
trinhminhtriet
moshe weitzman
matt.c
Patrick Storey
nick.morahan
dave bruns
nitin.k volunteering
pio.fernandes
kvu@csusm.edu
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.