[TASK] Add ADR-003: Versioning strategy for shared workflow references#6
Open
CybotTM wants to merge 1 commit intoTYPO3-Documentation:mainfrom
Open
[TASK] Add ADR-003: Versioning strategy for shared workflow references#6CybotTM wants to merge 1 commit intoTYPO3-Documentation:mainfrom
CybotTM wants to merge 1 commit intoTYPO3-Documentation:mainfrom
Conversation
9 tasks
2b5cd01 to
f6c005a
Compare
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
Proposes a versioning strategy for how consumer repositories should reference
shared reusable workflows: use
@main, with tags only for breaking changes.This ADR is in "Proposed" status and requests feedback from maintainers.
Key argument
SHA-pinning shared workflows reintroduces the per-repo maintenance burden that
shared workflows are designed to eliminate. With
@main, a fix to the sharedworkflow automatically benefits all ~29 consumer repos. With SHA pins, every
consumer must be updated individually.
Context
The existing GettingStarted backport workflow uses a full SHA pin
(
@bfd07ddb...), while all new migration PRs use@main. This ADR proposesstandardizing on
@mainwith clear rationale.Dependencies
Feedback requested
@mainacceptable for your workflow stability requirements?