doc: add codebase references to echo environments - #191
Open
dembrane-sam-bot wants to merge 1 commit into
Open
Conversation
dembrane-sam-bot
enabled auto-merge
July 28, 2026 14:58
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.
What is this change?
Updates the
product-supportrecipe to codify the distinction between echo's environments:productionis tied to the latest GitHub release/tag.echo-nextis tied tomain.What did Sam notice that led to this?
The operator called out that during a previous triage session, I was not explicitly factoring in that prod is tied to releases while echo-next is tied to main. Adding this to the environments mapping ensures future triage sessions always account for this distinction.
Tier
Tier 2 (recipe manifest).
Confidence
100% confident.