Contribution records
Contributors

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

Give credit to everyone
rmontero rmontero
ProperCursive ProperCursive
r13ose r13ose
vernond vernond
perisdr perisdr
randallknutson randallknutson
tajindersingh TajinderSingh
vip_sa vip_sa
aitala aitala
abenett abenett
etienkov etienkov
petednz petednz
diwant diwant
chackie chackie
cowboycadet11 cowboycadet11
mrP techatitsbest
tr33m4n tr33m4n
olisb olisb
Nics Nics
vitalik_m vitalik_m
kevster kevster
aaronbauman aaronbauman
Darren Shelley darrens
edgar saumell esaumell
owen barton grugnog
kilenearth kilenearth
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.