Skip to content

WIP: upstream rebase conflict — manual resolution needed#14

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
auto/rebase-conflict
Open

WIP: upstream rebase conflict — manual resolution needed#14
github-actions[bot] wants to merge 1 commit into
mainfrom
auto/rebase-conflict

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented Jun 1, 2026

scripts/rebase-upstream.sh exited non-zero for at least one
submodule. Manual hunk resolution required — see the affected
submodule working tree(s) for unmerged paths. The script log names
which submodule stopped and the git am --continue recovery steps.

@github-actions github-actions Bot force-pushed the auto/rebase-conflict branch from 6e4d816 to e7549fb Compare June 3, 2026 00:28
@github-actions github-actions Bot changed the title WIP: llama.cpp rebase conflict — manual resolution needed WIP: upstream rebase conflict — manual resolution needed Jun 3, 2026
sunrunnerfire added a commit that referenced this pull request Jun 3, 2026
The rebase script (both before and after the 4-submodule generalization)
snapshotted the *working tree* to build the replay series, assuming
apply-patches.sh had run first. In CI the submodules are checked out at their
pinned SHAs with no patches applied, so the snapshot was empty: the script
reset to upstream and then 'git am'-ed an empty series, producing a spurious
conflict on every run. The original PR #14 'conflict' was this bug, not real
upstream drift.

Apply patches/<submodule>/*.patch directly onto the freshly-reset upstream via
git am -3 — the committed patch files are the source of truth, no working-tree
dependency. Preserve the curated patch filenames on regeneration (positional,
since series order is stable) so doc references and the 0001/0002 numbering
don't churn. Validated locally: clean apply onto the pinned base, filename
preserved, content identical.
@github-actions github-actions Bot force-pushed the auto/rebase-conflict branch from e7549fb to 58e1722 Compare June 3, 2026 00:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant