Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
ray007
karens
GregoryHeller
cardentey
PRZ
gunzip
wundo
strykaizer
visualnotion
introfini
jrust
klahaeck
digitalproductionart
seabrawk
li8461
JamieR
doknet
akolahi
tteller
browlands
patrickfrickel
calbasi
iSheng
jackfoust
bobgeier
rlnorthcutt
truyenle
bsztreha
murz
basvredeling
peterparker
askibinski
Tokoh
miro_dietiker
jhodgdon
acouch
ayalon
pragnatek
k3n3dy
MBroberg
westie
sdsheridan
delty
frishaynes
portulaca
petednz
adamtong
fmesco
hallg9999
jiakomo
deejmer
AndreasST
Niremizov
jcam88
dbassendine
CandC540
dobrzyns organization(s): Promet Source
Kleinast volunteering
big_smile
kristofferwiklund
kharbat
delacosta456
moshe weitzman
Daniel A. Beilinson
aren cambre
henrijs.seso
steel-track
inky@inky3d.com
daniels____
Sinan Erdem
Andrew Edwards
jason.fisher
uwe mindrup
scott.browne
Pierre.Vriens
sun
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.