Contribution records
Contributors

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

Give credit to everyone
quicksketch quicksketch
mooffie mooffie
janusman janusman
tuti tuti
techninja techninja
mitchell mitchell
jiakomo jiakomo
3lite 3lite
dropchew dropchew
chirale chirale
jwilson3 jwilson3
szy szy
sun sun
nilard Nilard
criz criz
chilledoutbeardedman chilledoutbeardedman
parrottvision parrottvision
marvix marvix
cashwilliams CashWilliams
jrust jrust
AlxM AlxM
mattiasj mattiasj
gulliverrr gulliverrr
ultimike ultimike
swentel swentel
pvhee pvhee
dirksonii dirksonii
turadg turadg
mcpuddin mcpuddin
jhedstrom jhedstrom
crea crea
luksak luksak
fumbling fumbling
newacct newacct
BenK benk
thebuckst0p thebuckst0p
Sepero Sepero
derhasi derhasi
codigovision CodigoVision
JayShoe JayShoe
jenlampton jenlampton
Mike Sances Mike_Sances
moshe weitzman weitzman
Coupon Code Swap undoIT
ju.ri ju.ri
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.