Skip to content

chore: migrate to the reusable leanprover-community/intentions workflow#77

Open
kim-em wants to merge 1 commit into
b-mehta:mainfrom
kim-em:chore/reusable-intentions
Open

chore: migrate to the reusable leanprover-community/intentions workflow#77
kim-em wants to merge 1 commit into
b-mehta:mainfrom
kim-em:chore/reusable-intentions

Conversation

@kim-em

@kim-em kim-em commented Jun 23, 2026

Copy link
Copy Markdown

This PR replaces the four copied 01-claim-issue04-withdraw-pr workflows with a single caller of the maintained reusable workflow at https://github.com/leanprover-community/intentions (pinned to @v1; see the announcement). Your 05-awaiting-review.yml (awaiting-review) workflow is independent of these four files and is left untouched. The claim / disclaim / propose PR / withdraw PR vocabulary and the project board are unchanged, so contributors notice nothing.

Setting default-ttl: none preserves the current "claims never expire" behavior: there are no board changes, no Claim Expires field, and no scheduled sweep.

It reuses your existing PAT_TOKEN secret, so no new secrets are needed. That token is now used only for the Projects v2 board; issue assignment and comments run on the workflow's built-in GITHUB_TOKEN (granted issues/pull-requests write in the caller), exactly as the old workflows did — so PAT_TOKEN only needs Projects access.

Two optional follow-ups, not included here: the action can also drive the full board lifecycle (auto-add issues, PR-driven status, completion on merge) and automatic claim expiry — see the README if you ever want either. And if your organization restricts Actions to "this organization only", allow leanprover-community/intentions in Settings → Actions so the reusable workflow can run.

🤖 Prepared with Claude Code

Replace the copied 01-claim-issue..04-withdraw-pr workflows with one caller of
the maintained reusable workflow. Command vocabulary and the board are
unchanged; default-ttl: none preserves "claims never expire", so no board
changes are needed. Reuses the existing PAT_TOKEN for the Projects board only;
issue assignment and comments use the workflow GITHUB_TOKEN.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant