Issue
Contribution records
Contributors

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

Give credit to everyone
Steven
kastaway
rosenblum68
ahoeben
jacauc
drumm
msmiffy
csevb10
agentrickard
catch
underpressure
alpha2zee
cburschka
jdefay
TimAlsop
dominich
bradnana
GetActive
domesticat
cvining
packdragon
alex_b
jeffschuler
MichaelCole
s4j4n
gausarts
smscotten
David_Rothstein
xjm
dries
andypost
sun
pillarsdotnet
patcher
aascherson
lundj
fbreckx
rtrubshaw
chirikamo17640
ggevalt
webengr
mimes
guillaumeduveau
gojensen
mediaformat
poker10 organization(s): ActivIT s.r.o.
Steve Dondley
Roadskater.net
matt westgate
edmund.kwok
ezra-g
problue solutions
jody lynn
dave reid
albert volkman
liam morland
Irene Meisel
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.