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: #195, #201, #200, #202, #199 #715

Closed
magic-mirror-bot bot opened this issue Feb 14, 2024 · 0 comments · Fixed by #716
Closed

😿 Failed to sync the upstream PRs: #195, #201, #200, #202, #199 #715

magic-mirror-bot bot opened this issue Feb 14, 2024 · 0 comments · Fixed by #716
Assignees

Comments

@magic-mirror-bot
Copy link

🪞 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/config-policy-controller until the issue is manually resolved and this issue is closed.

Syncing error:

Error: Auto-merging .github/workflows/kind.yml
CONFLICT (content): Merge conflict in .github/workflows/kind.yml
CONFLICT (modify/delete): .github/workflows/go-release.yml deleted in HEAD and modified in 9d7e595 (Bump the github-actions group with 2 updates). Version 9d7e595 (Bump the github-actions group with 2 updates) of .github/workflows/go-release.yml left in tree.
CONFLICT (modify/delete): .github/workflows/go-postsubmit.yml deleted in HEAD and modified in 9d7e595 (Bump the github-actions group with 2 updates). Version 9d7e595 (Bump the github-actions group with 2 updates) of .github/workflows/go-postsubmit.yml left in tree.
CONFLICT (modify/delete): .github/workflows/fossa.yml deleted in HEAD and modified in 9d7e595 (Bump the github-actions group with 2 updates). Version 9d7e595 (Bump the github-actions group with 2 updates) of .github/workflows/fossa.yml left in tree.
error: could not apply 9d7e595... Bump the github-actions group with 2 updates
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'

Commands to recreate the issue:

git cherry-pick -x 8f18c31867bdf0f7e54a2bce6f9f196a502146a4~1..8f18c31867bdf0f7e54a2bce6f9f196a502146a4 --allow-empty --keep-redundant-commits
git cherry-pick -x a4f7286ac73e86a8755aa1475d831faceee7f28e~1..a4f7286ac73e86a8755aa1475d831faceee7f28e --allow-empty --keep-redundant-commits
git cherry-pick -x f6be8e7945b856e7ede9eb14815ed24638cf2a7b~1..f6be8e7945b856e7ede9eb14815ed24638cf2a7b --allow-empty --keep-redundant-commits
git cherry-pick -x 9d7e595309ba2fee1f2235c35647766e8f7c6b36~1..9d7e595309ba2fee1f2235c35647766e8f7c6b36 --allow-empty --keep-redundant-commits
git cherry-pick -x 41aa493d21655bcb8c605c7147764d2439c7ca89~1..41aa493d21655bcb8c605c7147764d2439c7ca89 --allow-empty --keep-redundant-commits

sad Yoda

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

Successfully merging a pull request may close this issue.

1 participant