Skip to content
github-actions

All versions since 0.2.0

All versions

0.2.0

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Added

  • derive.py --rulesets compares the ruleset and required check concepts with the rulesets GitHub returns, and --check-runs compares the required checks with what one commit recorded. scripts/github_export.py prints both from the REST API, as Markdown that a host’s ingest can mirror.
  • derive.py --check counts as drift a skip condition that a required check’s body does not name. It no longer looks for a workflow behind a check that another app reports.

Fixed

  • A path filter, or a calling job’s if or needs, leaves a required check pending, which blocks the merge. derive.py’s findings and the GhaRequiredStatusCheck comment said that every skip reported success.
  • derive.py counts a job’s needs as a skip condition, and no longer counts if: always(). A failed or skipped dependency skips the job, so its check passes without running.

0.2.1 Latest

As it stood at this release: the repository · the docs · the knowledge bundle · the release

Fixed

  • Three concepts pin #7’s squash commit, which main holds, so the knowledge release attaches its assets again. Each pinned a pull request commit that the squash merge left out, which stopped v0.2.0’s knowledge release.