Contribution records
Contributors

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

Give credit to everyone
guy_schneerson guy_schneerson
swentel swentel
podarok podarok
czigor czigor
yched yched
berdir berdir
yesct YesCT
sidharthap sidharthap
jair jair
durifal durifal
mcrittenden mcrittenden
alexkb alexkb
xano Xano
catch catch
paranojik paranojik organization(s): Cando
anrikun anrikun
poker10 poker10 organization(s): ActivIT s.r.o.
quietone quietone organization(s): PreviousNext
David Hernández David_Hernandez
Rajesh Ashok RajeshAshok
gábor hojtsy goba
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.