Skip to content
Latchkey

Python Linter workflow (secretflow/secretflow)

The Python Linter workflow from secretflow/secretflow, explained and optimized by Latchkey.

C

CI health: C - fair

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: secretflow/secretflow.github/workflows/black.ymlLicense Apache-2.0View source

What it does

This is the Python Linter workflow from the secretflow/secretflow 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: Python Linter
on:
  push:
    branches:
    - main
  pull_request:
    branches:
    - main
jobs:
  python-linter:
    uses: secretflow/.github/.github/workflows/python-linter.yml@main

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

---
name: Python Linter
on:
  push:
    branches:
    - main
  pull_request:
    branches:
    - main
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  python-linter:
    timeout-minutes: 30
    uses: secretflow/.github/.github/workflows/python-linter.yml@main
 

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.

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