Contribution records
Contributors

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

Give credit to everyone
kanani kanani
robdubparker plinthify
goldenboy goldenboy
scotwith1t phrancescot
rongok rongok
chrsnlsn chrsnlsn
jibran jibran volunteering
dawehner dereine
pmcdougl pmcdougl
wooody wooody
solesum solesum
aquasplash aquasplash
koechsle koechsle
cracu Cracu
discipolo discipolo
tstoeckler tstoeckler organization(s): erdfisch
brightbold brightbold
mustanggb akamustang
damienmckenna damienmckenna organization(s): Current
LAguilar LAguilar
lunk rat LunkRat
s.reichert s.reichert
tessa bakker TessaBakker organization(s): ezCompany
alex.skrypnyk alex.skrypnyk volunteering
a.milkovsky milkovsky organization(s): drunomics
André Ferreira André Ferreira
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.