Contribution records
Contributors

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

Give credit to everyone
larowlan larowlan
nod_ nod_
effulgentsia effulgentsia
Bojhan bojhan
yched yched
swentel swentel
tsvenson tsvenson
seutje seutje
webchick webchick
jelle_s jelles
mustanggb akamustang
mgifford mgifford
dasjo dasjo
quicksketch quicksketch
tstoeckler tstoeckler
sun sun
fabianx Fabianx
yoroy yoroy
rvilar rvilar
falcon03 falcon03
dries dries
xjm xjm
jessebeach jessebeach
catch catch
jibran jibran
andypost andypost
klonos klonos
tim.plunkett tim.plunkett
user advocate useradvocate
scott.gonzalez scott.gonzalez
Dean Reilly DeanReilly
jason.fisher jason.fisher
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.