Contribution records
Contributors

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

Give credit to everyone
Emkas Emkas
offal offal
bhosmer bhosmer
tbayens tbayens
jeremyvanlanda jeremyvanlanda
tvilms tvilms
rivimey rivimey
deviantintegral deviantintegral
benstallings BenStallings
jh3 ejh3
davapiano davapiano
rlmumford rlmumford
Z2222 hostels
scito scito
amontero amontero
nikosnikos niconico
matthewdolman matthewdolman
beetlewing beetlewing
webadpro webadpro
Roedelhorst Roedelhorst
nickvidal nickvidal
mrcniceguy mrcniceguy
Funksmaname Funksmaname
mrtoner mrtoner
vordude vordude
luco luco
lukio lukio
fdambrosio fdambrosio
scurvy scurvy
markie markie organization(s): Current
glass.dimly glassdimly
Anthony Pero ConvergentCreative
saikatewu@gmail.com saikatewu volunteering
BillMounce BillMounce
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.