Contribution records
Draft
Contributors

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

Give credit to everyone
altparty altparty
kyle_mathews kylemathews
presencia presencia
noelbush noelbush
RikiB RikiB
sdemircan sdemircan
tevih tevih
fizk fizk
orizu orizu
sherryheinz sherryheinz
petednz petednz
lolmaus lolmaus
BMorse BMorse
neochief neochief
rbl rbl
atuline atuline
alpersari alpersari
jeremy Jeremy
Michsk Lasac
tsorelle tsorelle
tibbsa tibbsa
tribsinpa tribsinpa
christefano christefano
edvanleeuwen edvanleeuwen
linuxpimp linuxpimp
David Goode davidg
dyke it dyke it
jason.fisher jason.fisher
shraddha.sawant shraddha.sawant
jose reyero reyero
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.