Contribution records
Contributors

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

Give credit to everyone
chx chx
stevector stevector
jenlampton jenlampton
c4rl c4rl
effulgentsia effulgentsia
fabianx Fabianx
podarok podarok
catch catch
jwilson3 jwilson3
younger870 younger870
steveoliver steveoliver
attiks attiks
kika kika
amateescu amateescu
webchick webchick
dozymoe dozymoe
mortendk mortendk
swentel swentel
Crell Crell
sun sun
dries dries
cosmicdreams cosmicdreams
cweagans cweagans
David_Rothstein drothstein
KrisBulman KrisBulman
webflo webflo
schnitzel Schnitzel
jhodgdon jhodgdon
johnalbin johnalbin
xjm xjm
bhagath bhagath volunteering
geerlingguy geerlingguy
quietone quietone organization(s): PreviousNext
vlad.dancer vlad.dancer
moshe weitzman weitzman
rene bakx rene.bakx
tim.plunkett tim.plunkett
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.