Repository navigation
Conversation
Contributor
Author
|
@redox this is the follow-up from the Slack thread: it makes Slack no-op heartbeats return exactly |
redox
approved these changes
Jul 10, 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
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.
Summary
NO_REPLYwhen there is no human-facing Slack actionHEARTBEAT_OKlimited to non-Slack/internal heartbeat invokersRationale
PR #59 said routine heartbeat runs should be silent in Slack, but the 14:00 UTC regular heartbeat still posted a no-op summary. The missing operational detail is that when a heartbeat would emit to Slack and has no Slack-visible action, the final response must be
NO_REPLY; this makes that explicit where heartbeat and Slack communication rules are read.Validation
bash scripts/validate-workspace.shmake lint