Contribution records
Contributors

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

Give credit to everyone
catch catch
Bojhan bojhan
jacine Jacine
cha0s cha0s
David_Rothstein drothstein
tgeller tgeller
horncologne horncologne
EvanDonovan evandonovan
yoroy yoroy
sun sun
rgristroph rgristroph
Remon rgeorgy
yesct YesCT
webchick webchick
aspilicious aspilicious
tstoeckler tstoeckler
philbar philbar
iantresman iantresman
aaronbauman aaronbauman
matason matason
Stevel stevel
patrickfgoddard thund3rbox
gdd heyrocker
chx chx
willmoy willmoy
bleen bleen18
giorgio79 giorgio79
kaakuu kaakuu
ronald_istos istos
Letharion Letharion
bojanz bojanz
int int
janusman janusman
mikey_p mikey_p
steinmb steinmb
mfer mfer
gábor hojtsy goba
mike stewart mdrmike
Maxim Rosca Maxim_Rosca
moshe weitzman weitzman
snorkers snorkers
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.