fix: deduplicate commit statuses in get_combined_status #16

Merged
john merged 1 commit from feat/fix-combined-status-dedup into dev 2026-06-13 07:33:49 +00:00
Owner

get_combined_status checked ALL historical statuses instead of deduplicating by context. Stale pending entries from earlier CI runs poisoned the combined result, causing the merge sweep to skip PRs with passing CI (bug-reporter 9 PRs stuck).\n\nBumps haskytech-forgejo to 0.1.2.

get_combined_status checked ALL historical statuses instead of deduplicating by context. Stale pending entries from earlier CI runs poisoned the combined result, causing the merge sweep to skip PRs with passing CI (bug-reporter 9 PRs stuck).\n\nBumps haskytech-forgejo to 0.1.2.
fix: deduplicate commit statuses in get_combined_status
All checks were successful
CI / detect-changes (pull_request) Successful in 4s
CI / Lint & Format (pull_request) Successful in 7s
CI / Unit Tests (pull_request) Successful in 11s
25c195dafe
The method checked ALL historical statuses instead of deduplicating
by context (taking latest per-job). One stale pending entry from an
earlier CI run would poison the combined result, causing the merge
sweep to skip PRs with passing CI.

Uses the same first-seen dedup as get_per_job_statuses.
Bumps haskytech-forgejo to 0.1.2.
john merged commit 20e00b53db into dev 2026-06-13 07:33:49 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
haskytech/haskytech-modules-py!16
No description provided.