Issue
Contribution records
Contributors

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

Give credit to everyone
chx
sun
webchick
pwolanin
Leeteq
marcushenningsen
translector
TCRobbert
mcrittenden
adamo
entr3p
rsvelko
donquixote
hanoii
joshk
indytechcook
servantleader
jolidog
AdrianB
darrellduane
supersteph
klonos
berdir
jannalexx
choster
guypaddock
xano
catch
int
yoroy
vensires
EvanDonovan
marcvangend
CYD
DRIVE
effulgentsia
brewthis
tinny
ngottlieb
wiredescape
bryrock
SilviaT
pillarsdotnet
quicksketch
LarsKramer
jviitamaki
justmagicmaria
lpalgarvio
mrfelton
mbutelman
mkadin
giorgio79
anrikun
JonoB
gpk
fjs
xjm
corvus_ch
liquidcms
kerasai
jrglasgow
zakiya
disasm
JimmyAx
jvieille
mgifford
dawehner
merlinregis
rootwork
colinstillwell
The_Bucks
moshe weitzman
Gary Feldman
smk-ka
Daniel Norton
damien tournoud
David D
alex malkov
thomas.fleming organization(s): Last Call Media
hey-pingu
joseph.olstad
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.