Commit 127ca3a
Build from the base branch, not just target it
CodeRabbit caught this on the multisite PR and it applies identically here:
`base` only set the PR target, while actions/checkout took no ref at all. Since
create-pull-request commits onto whatever HEAD it finds, dispatching from
feature/foo with base develop would build feature/foo and then raise a PR into
develop containing every commit between the two - not just the POT change.
Checkout now uses the same `base` expression, so one value decides what gets
built, what the PR branch is named, and what it targets. There is no
combination of inputs that makes them disagree.
The develop default is dropped from the input at the same time: with base now
driving the checkout, a hardcoded default would silently ignore the branch
picked in the dispatch UI. Empty falls back to the dispatched branch, so the
picker behaves as expected and build and target still match.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019LoLgW7oFjBPxGea9kiZJ21 parent 7954422 commit 127ca3a
1 file changed
Lines changed: 9 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
7 | | - | |
| 7 | + | |
8 | 8 | | |
9 | | - | |
10 | 9 | | |
11 | 10 | | |
12 | 11 | | |
| |||
16 | 15 | | |
17 | 16 | | |
18 | 17 | | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
19 | 23 | | |
20 | 24 | | |
| 25 | + | |
| 26 | + | |
21 | 27 | | |
22 | 28 | | |
23 | 29 | | |
| |||
103 | 109 | | |
104 | 110 | | |
105 | 111 | | |
106 | | - | |
| 112 | + | |
107 | 113 | | |
108 | 114 | | |
0 commit comments