Package Exports

git-auto-badger

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (git-auto-badger) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Git Auto badger

A npm cli tool that reads your packagejson and git config and connects your readme with multiple badge providers (shields.io, badgen.net etc)

This is still a WIP

How to use

    npm i -g git-auto-badger

Add following markdown comment where you want the badges to appear

[//]: <> (start placeholder for auto-badger)

then run following in your project root directory

    npx auto-badger

This cli currently supports following providers from each category

VCS
- Github [✔️]
- Gitlab [Coming soon]
CI/CD
- Travis CI [✔️]
- Github Actions [Coming soon]
- Appveyor [Coming soon]
- Circle CI [Coming soon]
Coverage
- Coveralls [✔️]
- CodeCov [Coming soon]
Package Managers
- NPM [✔️]
- PyPI [Coming soon]
License
- Github License File [✔️]
Code of Conduct
- Github CoC File [✔️]
Dependancies
- Libraries.io for NPM [✔️]
Package size
- Bundelphobia [✔️]
Download Count
- NPM Per month [✔️]
Social
- Github (Repo Stars, Fork) [✔️]
- twitter [Coming soon]

How it works?

It looks for different file in your project root directory. To decide what tools are you using. And generates badges based on it. e.g. If you have .travis.yml then it assumes you are using travis for CI/CD and it creates a dynamic badge for travis latest build status