Commit 3314aa6
Fix e2e merge-command assertion broken by the ff-only step (#44)
Since #40 the conflict comment's fast-forward step reads `git merge
--ff-only origin/<branch>`, which `assert_conflict_comment_merges` picks
up with its `^git merge` grep, so the extracted commands never match the
expected conflict merges and the check fails on every conflict scenario.
#40's test tweak only handled the new `# ...` hash gloss, not the new
merge line.
This went unnoticed because `tests.yml` only runs on `pull_request`, so
the breakage only surfaced on the first PR after #40 landed (#42, [run
27235483781](https://github.com/scortexio/autorestack-action/actions/runs/27235483781)).
Fix: skip the `--ff-only` line when extracting merge commands. Verified
green as part of #42's [run
27235912022](https://github.com/scortexio/autorestack-action/actions/runs/27235912022)
before being split out into this PR.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01JHvKryT4QUpHYdNq9YEQxX
---
_Generated by [Claude
Code](https://claude.ai/code/session_01JHvKryT4QUpHYdNq9YEQxX)_
Co-authored-by: Claude <noreply@anthropic.com>1 parent 2d2469a commit 3314aa6
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
291 | 291 | | |
292 | 292 | | |
293 | 293 | | |
294 | | - | |
| 294 | + | |
295 | 295 | | |
296 | 296 | | |
297 | 297 | | |
| |||
0 commit comments