Contribution records
Contributors

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

Give credit to everyone
valthebald valthebald
Bojhan bojhan
cossovich cossovich
webchick webchick
David_Rothstein drothstein
adnasa adnasa
sphism sphism
chrisjlee chrisjlee
cweagans cweagans
lewisnyman lewisnyman
yesct YesCT
tkoleary tkoleary
nod_ nod_
geodaniel geodaniel
lslinnet lslinnet
yoroy yoroy
ry5n ry5n
aspilicious aspilicious
xano Xano
dries dries
lucascaro lucascaro
larowlan larowlan
jenlampton jenlampton
alexpott alexpott
wusel wusel
nilnullvoid nilnullvoid
chx chx
catch catch
klonos klonos
jessebeach jessebeach
yannickoo yannickoo
gábor hojtsy goba
moshe weitzman weitzman
wim leers wimleers
tim.plunkett tim.plunkett
damien tournoud damz
star-szr star-szr
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.