/coverage-badge-py

:octocat: Github action to generate coverage badge without uploading results to a 3rd party.

MIT LicenseMIT

Codacy Badge CI Update release version. Public workflows that use this action.

Ubuntu Mac OS

coverage-badge-py

Generate coverage.py badge like this coverage badge without uploading results to a 3rd party site.

Usage:

...
    steps:
      - uses: actions/checkout@v2
      - name: Coverage Badge
        uses: tj-actions/coverage-badge-py@v1.8

NOTE: ⚠️

  • It's important that you run this action from the directory where the .coverage data file is located.

If you feel generous and want to show some extra appreciation:

Support this project with a

Buy me a coffee

Inputs

INPUT TYPE REQUIRED DEFAULT DESCRIPTION
output string true "coverage.svg" Output path to write the
coverage badge.
overwrite string true "true" Overwrite an existing coverage badge.

Example

...
    steps:
      - uses: actions/checkout@v2
        with: 
          fetch-depth: 0

      - name: Coverage Badge
        uses: tj-actions/coverage-badge-py@v1.8

      - name: Verify Changed files
        uses: tj-actions/verify-changed-files@v9
        id: changed_files
        with:
          files: coverage.svg

      - name: Commit files
        if: steps.changed_files.outputs.files_changed == 'true'
        run: |
          git config --local user.email "github-actions[bot]@users.noreply.github.com"
          git config --local user.name "github-actions[bot]"
          git add coverage.svg
          git commit -m "Updated coverage.svg"

      - name: Push changes
        if: steps.changed_files.outputs.files_changed == 'true'
        uses: ad-m/github-push-action@master
        with:
          github_token: ${{ secrets.github_token }}
          branch: ${{ github.ref }}

TODO

  • Add support for running action on Windows

Credits

This package was created with Cookiecutter.

Report Bugs

Report bugs at https://github.com/tj-actions/coverage-badge-py/issues.

If you are reporting a bug, please include:

  • Your operating system name and version.
  • Any details about your workflow that might be helpful in troubleshooting.
  • Detailed steps to reproduce the bug.