Support non-force branch update strategy for protected automation branches #2

New issue

Closed

opened 2026-06-16 17:54:53 +00:00 by stephen · 0 comments

stephen commented

2026-06-16 17:54:53 +00:00

Owner

Why

The action always force-pushes the head branch when updating an existing PR. Some repos protect automation branches or require linear history without force updates.

Verified

MIGRATION.md says the branch update strategy is force-push and has no separate strategy input.
src/main.js update path works on the target branch and pushes, with no update-strategy option visible.
No existing create-pull-request-action issues are filed.

Build

Add an input for branch-update-strategy such as force, rebase, or fail-if-diverged.
Fail clearly when branch protection rejects the selected mode.
Add tests for existing PR update behavior.

## Why The action always force-pushes the head branch when updating an existing PR. Some repos protect automation branches or require linear history without force updates. ## Verified - `MIGRATION.md` says the branch update strategy is force-push and has no separate strategy input. - `src/main.js` update path works on the target branch and pushes, with no update-strategy option visible. - No existing create-pull-request-action issues are filed. ## Build - Add an input for `branch-update-strategy` such as `force`, `rebase`, or `fail-if-diverged`. - Fail clearly when branch protection rejects the selected mode. - Add tests for existing PR update behavior.

stephen added the

opportunity

labels

2026-06-16 17:54:53 +00:00

stephen referenced this issue from a commit

2026-06-17 00:50:17 +00:00

Add push-strategy input for non-force branch updates

stephen referenced this issue from a pull request that will close it,

2026-06-17 00:50:26 +00:00

Support non-force branch update strategy #4

stephen closed this issue

2026-06-17 00:55:58 +00:00