Repository navigation
CI: assign every new issue and pull request to the maintainer - #81
Merged
Merged
Conversation
The workflow runs on issues and pull_request_target opened events and adds tae898 as assignee through the REST API. pull_request_target so a fork's pull request still gets a token that can edit it; nothing from the pull request head is checked out or run. A refused assignment logs a warning and does not fail the job. Closes #80 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
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.
Adds
.github/workflows/assign-maintainer.yml, which assigns every new issue and pull request totae898when it is opened (issue #80).It runs on
issues: openedandpull_request_target: openedand callsgithub.rest.issues.addAssigneesthroughactions/github-script, pinned to the same full SHA as the other workflows. I usepull_request_targetso a fork's pull request still gets a token that can edit it; nothing from the pull request head is checked out or run, the job only calls the GitHub API. An item that already hastae898assigned is skipped, and a refused assignment (a bot, a fork pull request) logs a warning and does not fail the job. No secrets, no checkout, no other action.I checked the file with
actionlintand parsed it with PyYAML. It will first be seen on the next new issue or pull request, since the events areopenedonly.Closes #80
🤖 Generated with Claude Code