You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Auto-merging .github/workflows/auto-upgrade-ci.yaml
Auto-merging .github/workflows/auto-version-release.yaml
Auto-merging .github/workflows/build-image-base.yaml
CONFLICT (content): Merge conflict in .github/workflows/build-image-base.yaml
Auto-merging .github/workflows/build-image-ci.yaml
CONFLICT (content): Merge conflict in .github/workflows/build-image-ci.yaml
Auto-merging .github/workflows/build-image-plugins.yaml
CONFLICT (content): Merge conflict in .github/workflows/build-image-plugins.yaml
Auto-merging .github/workflows/call-release-chart.yaml
Auto-merging .github/workflows/call-release-doc.yaml
CONFLICT (content): Merge conflict in .github/workflows/call-release-doc.yaml
Auto-merging .github/workflows/call-release-image.yaml
CONFLICT (content): Merge conflict in .github/workflows/call-release-image.yaml
Auto-merging .github/workflows/call-update-githubpages.yaml
Auto-merging .github/workflows/e2e-init.yaml
CONFLICT (content): Merge conflict in .github/workflows/e2e-init.yaml
Auto-merging .github/workflows/lint-golang.yaml
Auto-merging cmd/spiderpool/cmd/command_add.go
error: could not apply 0d6281101... Ensure kernel sends GARPs to avoid communication failures (#4681)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
The text was updated successfully, but these errors were encountered:
commits 0d62811 conflict when merging to branch release-v0.9, please manually cherry pick it by yourself.
PR #4681 , action https://github.com/spidernet-io/spiderpool/actions/runs/13493002697
The text was updated successfully, but these errors were encountered: