Contribution records
Contributors

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

Give credit to everyone
Golem07 Golem07
ytsuhako ytsuhako
holdmann holdmann
csc4 csc4
newad_fr newad_fr
mcartmel mcartmel
stg11 stg11
nobuyuki3 nobuyuki3
syawillim syawillim
dwhutton dwhutton
magpie5212 magpie5212
liliplanet Liliplanet
cbeier cbeier
artworker artworker
robstead robstead
Technikal Technikal
Leeteq Leeteq
fizk fizk
laur3ntlapo laur3ntlapo
barrabasah barrabasah
kenyan kenyan
xurizaemon xurizaemon
Bricks and Clicks Marketing Bricks_and_Clicks_Marketing
chris-cmfi chris-cmfi
tulasiraman tulasiraman
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.