Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TLDR
Humanize runs its full compatibility matrix for documentation and tooling-only changes. This PR skips unaffected complete jobs with pytest-selective and adds CI-esta reports so the decisions and runner usage are visible. The existing 27-job Python/OS matrix, tox commands, coverage and
Test successfulcheck are preserved.I benchmarked previous Humanize PRs before proposing this. Matched replays of a docs dependency update and a mypy update used 94.1% and 93.1% fewer core-workflow runner-seconds. A separate historical model estimates 26.7% lower usage across 19 PRs with five successful workflows, including planning and report overhead. Measured replays and estimates are separated below.
Existing action SHAs are unchanged. The new CI-esta and pytest-selective actions are pinned to the exact revisions used in the measured runs. No application runtime dependency is added.
Changes proposed in this pull request:
test:fulllabel override.Test successful.Measurements on real Humanize PRs
Each pair ran on an identical replay revision, with unchanged historical application code and the PR's original action SHAs. All five core workflows passed: Test, Benchmark, Release, Lint and Docs. All accepted runs are attempt 1. Lower runner usage is better.
Exact replay revisions and elapsed times
f94abc51d2c79afa864414a3d62359ef8f8d97b2e09a48c359d68ed4f8f2189b105c41176454ca6eb9064f43c9b978202ad7285d7b1bc35ef3ea168eHistorical workload estimate
The sample contains 20 recent merged PRs from 16 September through 2 November 2026, selected by merge time from the 100 most recently updated closed PRs. Seven would skip the runtime matrix. Every sampled source change retains it.
Per-PR historical data and source runs
Checks and maintainer controls
test:fullapplies on the next push/reopenTest successfulAbout the tooling
Disclosure: this contribution comes from the Gigaverse team, which maintains CI-esta and pytest-selective, and was prepared with Codex. CI-esta is open source under Apache-2.0 (license).
The underlying tooling has been used in Gigaverse's production CI for about five months across a Django monorepo and a Python microservices repository. It was extracted into the public packages more recently. The measured production history and approach are documented in Faster, cheaper CI: from the trenches.
The new refs are fixed to CI-esta 1.14.0 (
b694847) and pytest-selective 1.4.0 (286d0ae), the revisions resolved by the benchmark runs. The routing-test dependency is also pinned to pytest-selective 1.4.0.