fix: select the current SG heartbeat target and suppress unchecked summaries - #465
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.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
1 participant
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.
An enabled SG environment could be hidden by the repository's older multi-target Secret, causing the heartbeat to skip report checks and repeatedly send a misleading normal notification.
Prefer the explicit single target for an account-scoped heartbeat, retain multi-target selection for unscoped checks, and omit normal summaries when no target was checked. Malformed explicit configuration still fails rather than falling back to the old inventory.
Validation: reproduced four failures before the fix; 68 heartbeat, policy, runtime-guard and workflow tests pass, along with Ruff, lock validation and diff checks. No strategy, order or account configuration is changed.