Skip to content
Latchkey

Pydriller workflow workflow (ishepard/pydriller)

The Pydriller workflow workflow from ishepard/pydriller, explained and optimized by Latchkey.

F

CI health: F - at risk

Run this on Latchkey for self-healing, caching, and up to 58% lower cost.

Grade your own workflow free or run it on Latchkey →
Source: ishepard/pydriller.github/workflows/continuous-integration-workflow.ymlLicense Apache-2.0View source

What it does

This is the Pydriller workflow workflow from the ishepard/pydriller repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)
name: Pydriller workflow
on:
  push:
  pull_request:
  schedule:
    - cron: "0 0 * * *"

jobs:
  build:
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [ubuntu-latest, macOS-latest, windows-latest]
        python: [ '3.11.x', '3.12.x', '3.13.x', '3.14.x' ]
    name: Python ${{ matrix.python }} sample on ${{ matrix.os }}
    steps:
      - uses: actions/checkout@v2
      - name: Install python
        uses: actions/setup-python@v2
        with:
          python-version: ${{ matrix.python }}
      - name: Install dependencies and unzip test-repos
        run: |
          python -m pip install --upgrade pip
          pip install -r requirements.txt
          pip install -r test-requirements.txt
          pip install pytest-cov
          unzip test-repos
      - name: Mypy
        run: |
          pip install mypy
          mypy --ignore-missing-imports pydriller/ tests/
      - name: Lint with flake8
        run: |
          pip install flake8
          flake8
      - name: Run pytest
        run: pytest --junitxml=testpulse/test_run/test_results.xml --cov-report xml:testpulse/test_run/coverage.xml --cov=pydriller tests/
      - name: Upload coverage to Codecov
        uses: codecov/codecov-action@v4
        with:
          token: ${{ secrets.CODECOV_TOKEN }}
          file: coverage.xml

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: Pydriller workflow
on:
  push:
  pull_request:
  schedule:
    - cron: "0 0 * * *"
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: [ubuntu-latest, macOS-latest, windows-latest]
        python: [ '3.11.x', '3.12.x', '3.13.x', '3.14.x' ]
    name: Python ${{ matrix.python }} sample on ${{ matrix.os }}
    steps:
      - uses: actions/checkout@v2
      - name: Install python
        uses: actions/setup-python@v2
        with:
          cache: 'pip'
          python-version: ${{ matrix.python }}
      - name: Install dependencies and unzip test-repos
        run: |
          python -m pip install --upgrade pip
          pip install -r requirements.txt
          pip install -r test-requirements.txt
          pip install pytest-cov
          unzip test-repos
      - name: Mypy
        run: |
          pip install mypy
          mypy --ignore-missing-imports pydriller/ tests/
      - name: Lint with flake8
        run: |
          pip install flake8
          flake8
      - name: Run pytest
        run: pytest --junitxml=testpulse/test_run/test_results.xml --cov-report xml:testpulse/test_run/coverage.xml --cov=pydriller tests/
      - name: Upload coverage to Codecov
        uses: codecov/codecov-action@v4
        with:
          token: ${{ secrets.CODECOV_TOKEN }}
          file: coverage.xml
 

What changed

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

This workflow runs 1 job (12 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow