You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using automation that backports PRs from main to release branches if we label them with backport release/x.x.x. If a change set includes changelog entries, it fails in most cases to run successfully (like here). That forces us to resolve the conflict and do the backport manually.
The goal of this issue is to ensure there's automation that synchronizes CHANGELOG.md from main to all feature branches so the aforementioned conflicts are less frequent.
Proposed Solution
Use a GH workflow triggered by changes in the CHANGELOG.md on main that will propagate the changes to all feature branches (release/x.x.x).
Is there an existing issue for this?
Problem Statement
We're using automation that backports PRs from main to release branches if we label them with
backport release/x.x.x
. If a change set includes changelog entries, it fails in most cases to run successfully (like here). That forces us to resolve the conflict and do the backport manually.The goal of this issue is to ensure there's automation that synchronizes
CHANGELOG.md
from main to all feature branches so the aforementioned conflicts are less frequent.Proposed Solution
Use a GH workflow triggered by changes in the
CHANGELOG.md
on main that will propagate the changes to all feature branches (release/x.x.x
).https:/marketplace/actions/repo-file-sync-action seems to be capable of achieving something like that quite easily (sample config: https:/marketplace/actions/repo-file-sync-action#syncing-branches)
Additional information
No response
Acceptance Criteria
CHANGELOG.md
on every feature branch is synchronized with mainThe text was updated successfully, but these errors were encountered: