Contribution records
Contributors

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

Give credit to everyone
bryangullan makemineatriple
mayobutter mayobutter
moritzz moritzz
Antinoo Antinoo
marktheshark marktheshark
joetsuihk joetsuihk
andrewfn andrewfn
alexiswatson davidwatson
sun sun
mathis mathis
rmmcclay rmmcclay
Maguar Maguar
pouvoir pouvoir
rushala rushala
AdrianB AdrianB
Guru Sawant
aquila aquila
alternata99 alternata99
ami7878 ami7878
jhedstrom jhedstrom
cha0s cha0s
mrtoner mrtoner
j0rd j0rd
mcrittenden mcrittenden
angheloko angheloko
aaron aaron
ayalsule ayalsule
jokerejoker jokerejoker
stephenplatz stephenplatz
renamixtech renamixtech
tinem tinem
powery powery
klausi klausi
lucascaro lucascaro
srahul07 srahul07
maggie_au maggie_au
azzerpa azzerpa
dave reid davereid
harpreet.sahota harpreet.sahota
burt.lo burt.lo
kirtan-1 kirtan-1
harry slaughter hlslaughter
Git commit message
Commit types
  • 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

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.