Contribution records
Contributors

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

Give credit to everyone
alpinejag alpinejag
encho encho
Fayna Fayna
pbindagorge pbindagorge
alpritt alpritt
Moonshine moonshine
jonjob jonjob
Clarkmatic Clarkmatic
mikeryan mikeryan
vacilando Vacilando
jorditr JordiTR
sam6 sam6
danatang danatang
geodaniel geodaniel
AppleAp AppleAp
ryanoff ryanoff
scottrigby scottrigby
bsherwood bsherwood
Ostrea Ostrea
techutopia techutopia
tomceek tomceek
Lurple Lurple
yhager yhager
conniec conniec
dirkson dirkson
Shai Shai
avadhutp avadhutp
Starminder Starminder
summit summit
edward.peters edward.peters
Robrecht Jacques robrechtj
aren cambre arencambre
frank ralf frankralf
Coupon Code Swap undoIT
sammy-node sammy-node
allie micka vauxia
EllenM1-1 EllenM1-1
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.