Contribution records
Draft
Contributors

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

Give credit to everyone
pcambra pcambra
kensae kensae
ponies ponies
rtdean93 rtdean93
Griso81 Griso81
jasondecamp jasondecamp
bensti bensti
shaneonabike ShaneOnABike
agileadam agileadam
lima2x lima2x
Horroshow Horroshow
strings6 strings6
krisgraham thesaunterer
danadana danadana
babruix babruix
meecect meecect
xmacinfo xmacinfo
flocondetoile flocondetoile
cogent cogent
Frays Frays
slewazimuth slewazimuth
crabsoul rashmi08
Ante890 Ante890
stephenevans stephenevans
caw67 caw67
capfive capfive
IckZ IckZ
tj99ay tj99ay
Darren Shelley darrens
maciej.zgadzaj maciej.zgadzaj
a.hjelm a.hjelm
William Aubert william-aubert
Scott Robertson s-robertson
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.