Repository navigation
Add -assignees so new alert issues notify someone - #3
Merged
Merged
Conversation
Issues opened by the App notify nobody unless they watch the repository. -assignees (AGI_ASSIGNEES) takes comma-separated logins and sets them on create only; updates and closes are unchanged. Unset, the create request carries no assignees key, as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N1RroqyUFLEgadFTrFjLEi
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.
Requested by Andrew · project thread
Why
An issue opened by the GitHub App notifies nobody unless they watch the repository, so a new alert can go unseen.
What
-assignees(envAGI_ASSIGNEES): comma-separated GitHub logins set as assignees when an issue is created. Updates, comments and closes are unchanged.assigneeskey, so behaviour is exactly as before.TestAssigneesOnNewIssuecovers both cases: no key without the flag, and the logins passed through with it.Assigning only needs the issues permission the installation token is already narrowed to. GitHub drops an assignee who has no access to the repository.
Checked
gofmt -l .is clean,go vet ./...passes, andgo test -count=1 ./...passes.Releasing needs a
v0.2.0tag after merge. Cloud sessions can't create tags, so that step runs on MiniMac.Generated by Claude Code