feat: auto merge-to-main, bump-version workflow, and branch locking#154
Merged
petesramek merged 2 commits intodevelop/1.0from Apr 3, 2026
Merged
Conversation
…ource-branch validation Agent-Logs-Url: https://github.com/petesramek/polyline-algorithm-csharp/sessions/4418acb6-8233-47f4-9b0f-9f6f4de0fb09 Co-authored-by: petesramek <2333452+petesramek@users.noreply.github.com>
…kout to validate job, combine find commands, improve lock action error handling Agent-Logs-Url: https://github.com/petesramek/polyline-algorithm-csharp/sessions/4418acb6-8233-47f4-9b0f-9f6f4de0fb09 Co-authored-by: petesramek <2333452+petesramek@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
petesramek
April 3, 2026 18:21
View session
Copilot stopped work on behalf of
petesramek due to an error
April 3, 2026 18:23
Copilot stopped work on behalf of
petesramek due to an error
April 3, 2026 18:23
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.
The release-to-main promotion was manual and error-prone, with no way to determine which
release/**branch is "latest" without scanning all of them. Additionally, there was no automated way to start a new major/minor version cycle or enforce push restrictions on protected branches.merge-to-main (automatic)
merge-to-mainjob torelease.yml, runs only onrelease/**after GitHub Release is createdrelease/**branch viagit ls-remote | sort -V | tail -1M.mbefore comparing — only the latest branch triggers a PR tomainbump-version workflow
workflow_dispatchworkflow (bump-type: minor | major), must run frommainrelease/**branch; calculates nextM.mdevelop/M.mfrommainPublicAPI.Shipped.txtandPublicAPI.Unshipped.txtto#nullable enable— fresh API surface for breaking-change cyclesBranch locking
branch-protection/lock(sets PR-required + no force-push + no deletions via GitHub API) andbranch-protection/unlock(removes protection)promote-branch.ymlnow locks newly createdpreview/**andrelease/**branches immediately after the initial pushadministration: writepermission topromote-branch.ymlpromote-branch source-branch enforcement
develop/**orsupport/**branch could be promoted directly torelease/**preview←develop/**/support/**;release←preview/**only