Run: https://github.com/astral-sh/uv-dev/actions/runs/30299246211
Failed job: https://github.com/astral-sh/uv-dev/actions/runs/30299246211/job/90087981944
Workflow: Rebase conflicted pull requests
Job: Rebase pull request astral-sh/uv-dev#256 / Rebase pull request astral-sh/uv-dev#256
Platform: Depot Ubuntu 24.04
Attempt: 1
Decisive error:
fatal: Refusing to create empty bundle.
Process completed with exit code 128.
The rebase completed with a clean worktree and no active rebase, but HEAD and refs/remotes/origin/main both resolved to 116ca06b34b1f4e08ebf5f5cffa82599cbc664f0. The rebase output reported that the PR commit was dropped because its changes were already upstream. The verification step then unconditionally ran:
git bundle create "$RUNNER_TEMP/rebased.bundle" "refs/remotes/origin/$BASE_REF..HEAD"
Git cannot create a bundle from that empty revision range. This is a deterministic workflow edge case rather than a source test failure in #256. The workflow should explicitly handle a rebase whose commits all become empty, for example by reporting the no-op outcome without attempting to create an empty bundle.
The same run had an independent HTTP 403 while pushing the successfully rebased #253 branch. That failure is already tracked by #367.
Run: https://github.com/astral-sh/uv-dev/actions/runs/30299246211
Failed job: https://github.com/astral-sh/uv-dev/actions/runs/30299246211/job/90087981944
Workflow:
Rebase conflicted pull requestsJob:
Rebase pull request astral-sh/uv-dev#256 / Rebase pull request astral-sh/uv-dev#256Platform: Depot Ubuntu 24.04
Attempt: 1
Decisive error:
The rebase completed with a clean worktree and no active rebase, but HEAD and
refs/remotes/origin/mainboth resolved to116ca06b34b1f4e08ebf5f5cffa82599cbc664f0. The rebase output reported that the PR commit was dropped because its changes were already upstream. The verification step then unconditionally ran:Git cannot create a bundle from that empty revision range. This is a deterministic workflow edge case rather than a source test failure in #256. The workflow should explicitly handle a rebase whose commits all become empty, for example by reporting the no-op outcome without attempting to create an empty bundle.
The same run had an independent HTTP 403 while pushing the successfully rebased #253 branch. That failure is already tracked by #367.