Issue
Contribution records
Draft
Contributors

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

Give credit to everyone
drasgardian
drewish
jbrauer
eforth
NelM
infojunkie
jdelaune
vm
szb100
nicholasthompson
willazilla
mairav
dom_b
deciphered
jcnventura
p0pemar1naru
vannus
bkat
sierrawayfarer
cindyr
Archnemysis
henrykuo
berdir
old_dog
humanoc
skozik
alexiswatson
sun
marvil07
AdrianB
pieterdc
b3liev3
zilched
ChrisRut
jaxond
jantoine
osman
cyberwolf
leprechau
jaimealsilva
codekarate
mr_hossein
YK85
deng17
beatnikdude
spacereactor
Mascher
yan
twod
gansbrest
pkiraly
PatchRanger
elielcezar
mikebrooks
rwohleb
3soft
mrfelton
misc
cravecode
tm01xx
TmaX-2
danny englander
jbn
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.