jbonofre commented on PR #708:
URL: https://github.com/apache/camel-karaf/pull/708#issuecomment-5511061392
Rebased this branch onto current `main` (`60b7548e1`) and force-pushed, so
the PR is back on a linear history over the 11 commits `main` picked up since
`b79bba8ad`.
- The rebase was **conflict-free**, and the net diff is byte-identical to
the pre-rebase one (4 files, +125 / -0). Both commits are preserved; the
squash-merge will collapse them anyway.
- The CI failure on the previous head was `CamelGooglePubsubITest`, which is
unrelated to this change — it is fixed on `main` by 60b7548e1 ("bump the
Pub/Sub emulator image to a tag gcr.io still serves", #746). The rebase should
clear it.
- The PR description still describes the changeset accurately, so it is
unchanged.
@robinvish2794 heads-up: this PR's head is your fork's **`main`** branch, so
the force-push rewrote it. To sync your clone:
```
git fetch origin && git reset --hard origin/main
```
For future PRs, a topic branch (e.g. `fix-707-simple-no-file`) rather than
`main` avoids this.
_Claude Code on behalf of Jean-Baptiste Onofré_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
