Contribution records
Contributors

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

Give credit to everyone
momper momper
karens karens
yakker chrisyakimov
embirr embirr
Encarte Encarte
jerodfritz the7thsim
mikejonesok mikejonesok
bryanhidalgo bryanhidalgo
bardya bardya
lfrey lfrey
jhans jhans
Ingumsky Ingumsky
rlmumford rlmumford
jasom jasom
endiku endiku
2dareis2do 2dareis2do
wiizzard wiizzard
tribsel tribsel
btopro btopro
fmitchell fmitchell
diannaL diannaL
jayson jayson
johnlinux johnlinux
commonpike commonpike
wayne.gormont wayne.gormont
lucio.ferrari lucio.ferrari
tim.plunkett tim.plunkett
marcos.518 marcos.518
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.