chore(docs): update CI/CD docs for standard vs composable split#174
Open
chore(docs): update CI/CD docs for standard vs composable split#174
Conversation
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
Restructures the CI/CD documentation into two clear paths: a "standard" guide (
CICD-standard.md) for the recommended orchestrated workflows, and a "composable" guide (CICD-with-shared-actions.md) for teams that need fine-grained control over individual pipeline stages. Version references are updated from v2.0.3 to v3.2.0 throughout.The standard doc now leads with a mermaid sequence diagram and includes a full combined example (artifacts + docker + release bundle). The composable doc is repositioned as the "eject" path with detailed manual composition examples showing how
jf-build-idand artifact names must align between stages.Changes
Test plan
Docs-only change - no functional impact.