Contribution records
Contributors

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

Give credit to everyone
farald farald
trogie trogie
bdragon bdragon
yhzsailor yhzsailor
hubahubi hubahubi
that0n3guy that0n3guy
yesct YesCT
mjvesper mjvesper
jbizzay jasonalank
jhedstrom jhedstrom
pwieck pwieck
johnthomas00 johnthomas00
mvc mvc
steveadamo steveadamo
mswaringen mswaringen
sklausing sklausing
socialnicheguru SocialNicheGuru
strellman strellman
3goose 3goose
timl timl
rc2020 rc2020
nickbn nickbn
chriscalip chriscalip
sagannotcarl sagannotcarl
paj_mccarthy paj_mccarthy
fletch11 fletch11
bensheldon bensheldon
jrc jrc
goron goron
skyredwang skyred
aze2010 aze2010
nikovitto nikovitto
j0k3z j0k3z
matt2000 matt2000
jdln jdln
shopdogg shopdogg
tribe_of_dan tribe_of_dan
jeff.k jeff.k
henno.gous henno.gous
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.