Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

😿 Failed to sync the upstream PRs: #393 #1073

Closed
magic-mirror-bot bot opened this issue Apr 23, 2024 · 1 comment
Closed

😿 Failed to sync the upstream PRs: #393 #1073

magic-mirror-bot bot opened this issue Apr 23, 2024 · 1 comment

Comments

@magic-mirror-bot
Copy link
Contributor

🪞 Magic Mirror 🪞 failed to sync the following upstream pull-requests because one or more patches couldn't cleanly apply:

Syncing is paused for the branch main on stolostron/multicloud-operators-subscription until the issue is manually resolved and this issue is closed.

Syncing error:

Error: CONFLICT (modify/delete): .github/workflows/go-postsubmit.yml deleted in HEAD and modified in 847c2b5 (bump go lib to 1.21 (#393)).  Version 847c2b5 (bump go lib to 1.21 (#393)) of .github/workflows/go-postsubmit.yml left in tree.
CONFLICT (modify/delete): .github/workflows/go-presubmit.yml deleted in HEAD and modified in 847c2b5 (bump go lib to 1.21 (#393)).  Version 847c2b5 (bump go lib to 1.21 (#393)) of .github/workflows/go-presubmit.yml left in tree.
CONFLICT (modify/delete): .github/workflows/go-release.yml deleted in HEAD and modified in 847c2b5 (bump go lib to 1.21 (#393)).  Version 847c2b5 (bump go lib to 1.21 (#393)) of .github/workflows/go-release.yml left in tree.
Auto-merging build/Dockerfile
CONFLICT (content): Merge conflict in build/Dockerfile
Auto-merging build/Dockerfile.prow
CONFLICT (content): Merge conflict in build/Dockerfile.prow
Auto-merging build/Dockerfile.rhtap
CONFLICT (content): Merge conflict in build/Dockerfile.rhtap
error: could not apply 847c2b5... bump go lib to 1.21 (#393)
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".

Commands to recreate the issue:

git cherry-pick -x 847c2b5726492a47ec4c505e14f1c98e44f42d83~1..847c2b5726492a47ec4c505e14f1c98e44f42d83 --allow-empty --keep-redundant-commits

sad Yoda

@mikeshng
Copy link
Contributor

CC @xiangjingli

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant