Docs: CI/CD merge walkthrough + workflow_run explainer#248
Open
arielr-lt wants to merge 2 commits into
Open
Conversation
added 2 commits
May 20, 2026 08:41
The diagram already showed the high-level flow but didn't explain what happens on a real merge or how Release auto-triggers Deploy to TEST. Added a concrete timeline, the workflow_run trigger mechanics (including the head_sha checkout quirk), and a failure-modes table.
The doc covered apps and replicas but didn't say what nodes they run on or how the cluster bootstrap looks. Added a Nodes table (instance types and autoscale ranges per env), per-env EFS file system ids (matched to their Name tags so deploy-app.sh's auto-lookup is explicit), and a Cluster add-ons section listing the five Helm installs.
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.
Summary
Adds a concrete "what happens when you merge to main" timeline, explains the `workflow_run` trigger mechanism that auto-deploys to TEST after Release succeeds (including the head_sha checkout quirk), and a failure-modes table.
No code changes — docs only.