Repository navigation
ci: remove the assignees when an issue closes - #41
Merged
Merged
Conversation
Assignees stay on an issue after it closes unless someone removes them by hand, and closed issues that keep their assignee clutter every search by assignee. A workflow on the closed event of issues now removes them, whatever the close reason. It skips issues without assignees, so no runner starts for them. The workflow is an unchanged copy of the one that dnd-mapp/api-content piloted, so every dnd-mapp repository handles closed issues the same way. Closes #39
NoNamer777
enabled auto-merge
October 9, 2026 10:51
dnd-mapp-bot
approved these changes
Oct 9, 2026
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
2 participants
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.
Why
Every issue in the dnd-mapp org gets assigned to the account that works on it, and the assignee should come off once the issue closes. Today that is a manual step during the cleanup after a merge, and it is easy to forget. A closed issue that keeps its assignee clutters every search by assignee. dnd-mapp/api-content piloted a workflow that removes the assignees automatically, and this repository is one of the 14 that now adopt it.
What
A new
issue-closed.yamlworkflow runs when an issue closes and removes all its assignees with onegh issue edit --remove-assigneecall. It is a byte-for-byte copy of the file that dnd-mapp/api-content#44 merged, so every repository behaves the same and a later change can be copied the same way. It removes the assignees whatever the close reason, and it skips issues without assignees, such as the Dependency Dashboard of Renovate, so they start no runner. It needs onlyissues: writefromGITHUB_TOKEN, unlikeissue-opened.yaml, which needs a GitHub App token to write to the org project. It changes nothing that this repository publishes, so it needs no changelog entry.Test plan
pnpm run format-check,pnpm run lint-md, andactionlintpass locally, pluslint-ts,typecheck,test-ci, andbuild.Notes
The workflow only runs once it is on
main, so the last step of the test plan can only be followed after the merge. The pilot already proved the workflow in production on dnd-mapp/api-content#41.Closes #39