Mason DaughertyandGitHub 7eb2d8d6d8 ci: re-run require_issue_link check after PR reopen, close stale comments (#7403) ...

Combined:

(1)

After reopening a PR and removing the `missing-issue-link` label, the
`require_issue_link` check still shows as failed on the PR. Because the
default `GITHUB_TOKEN` suppresses event-driven re-triggers, the old red
check persists until the contributor pushes again. This adds a
best-effort re-run of the failed check so the PR's status clears
automatically on assignment.

(2)

When the `require_issue_link` workflow closes a PR and posts an
enforcement comment, that comment was never cleaned up after the
situation resolved — leaving a stale "automatically closed" message
visible on reopened PRs. Now all three resolution paths (maintainer
bypass, author fixing the issue link, and contributor assignment)
minimize the enforcement comment as outdated via GraphQL. The cleanup is
best-effort: failures log a warning but never block the primary workflow
logic (label removal, bypass, reopen).

2026-04-03 11:32:14 -04:00

..

actions/uv_setup

chore: extract reusable uv_setup composite action (#7262)

2026-03-24 00:25:58 -04:00

images

chore: new logos (#7002)

2026-03-02 11:59:44 -05:00

ISSUE_TEMPLATE

chore: extract reusable uv_setup composite action (#7262)

2026-03-24 00:25:58 -04:00

scripts

feat(cli): add keep_latest prune strategy to ThreadTTLConfig (#6784)

2026-02-11 19:00:48 -08:00

workflows

ci: re-run require_issue_link check after PR reopen, close stale comments (#7403)

2026-04-03 11:32:14 -04:00

dependabot.yml

chore: update dependabot.yml to comply with posture checks (#7278)

2026-03-25 10:59:11 -07:00

PULL_REQUEST_TEMPLATE.md

chore: update templates (#7261)

2026-03-24 00:17:49 -04:00

THREAT_MODEL.md

fix: moving threat model to .github/ (#7360)

2026-03-31 08:48:12 -04:00