docs: revert release-only first-class treatment in adoption guide - #256
Merged
Merged
Conversation
Signed-off-by: Joshua Temple <joshua.temple@stablekernel.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.
What
Reverts the four edits from #247 that gave release-only (no-env) mode a first-class treatment in the Adoption Guide. That detailed-docs treatment was more than warranted; the lighter touch belongs in the root README instead.
Scope
Restores the pre-#247 text in exactly four spots: the mental-model intro paragraph, the Prerequisites GitHub-setup bullet, the release-only note in the environment-choosing step, and the Topologies no-env bullet. The later #249/#250 "Splitting a monolithic pipeline" section and the validate/build/deploy/publish migration-table rows are untouched.
Verification