Cairn

CI fork PR token handling and comment posting fixes

NousResearch/hermes-agent · cluster 6679

Data as of

Nothing open on GitHub. Fix merged in #6681. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #6681. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #6681. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests address failures in CI workflows when running on fork PRs, where missing or inaccessible AUTOFIX_BOT_PAT tokens cause comment posting, label fetching, and supply chain audit steps to fail. The work involves adding fallback logic to use github.token when the bot PAT is unavailable.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #6681 fix(ci): don't fail supply chain scan when PR comment can't be posted on fork PRs

    merged to main

    files: .github/workflows/supply-chain-audit.yml

  • #66577 fix(ci): restore fork-safe token fallback on PR gates broken by #66373

    merged to main

    files: .github/actions/detect-changes/action.yml, .github/workflows/ci.yml, .github/workflows/lint.yml, .github/workflows/supply-chain-audit.yml

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #66560 fix(ci): fall back to github.token for the PR label fetch on fork PRs · done elsewhere → 1e01a4b, #66373, #66577
  • #66562 fix(ci): fall back to github.token when AUTOFIX_BOT_PAT empty on fork PRs · superseded by another PR → #66577
Closed issues · 2
  • Closed#6679[CI] Supply chain audit workflow fails on all fork PRs — GITHUB_TOKEN can't post comments
  • Closed#66559CI-sensitive file review fails on every fork PR: label fetch cannot read AUTOFIX_BOT_PAT
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#6681, #66577
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
17 Jul 2026

For your agent

The same facts, typed.

cluster/6679.json
cluster/6679.md