Repository navigation
Correct who an issue trigger email channel reaches - #119
Merged
Merged
Conversation
#116 and #118 said the email channel has no recipients of its own. The live API now accepts channels.email.member_emails: omitted or null means every eligible member, an empty array means nobody. The default triggers carry email: {}, so the conclusion stands, but the claim did not. Co-Authored-By: Claude Opus 5.5 <[email protected]>
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.
#116 and #118 said an issue trigger's email channel "has no recipients of its own". That is out of date. The live OpenAPI definition gives
IssueTriggerEmailChannelamember_emailsarray: omitted or null means all eligible members, and an empty array means nobody.The default triggers carry
email: {}, so muting them was still right and nothing in the code changes. Only the comments inproject-source.tsandAGENTS.mdare corrected.Follow-up, not in this PR:
alerting-001's scorer countsemail: {member_emails: []}as a notification channel. That belongs with the scorer defect being drafted from the trigger-precedence probe.🤖 Generated with Claude Code