exions / undo-push Goto Github PK

Hi, I have created an undo-push in GitHub action but it failed to do undo push. below the error logs.

Run exions/[email protected]
with:
branch: main
/usr/bin/docker run --name a33c17e2b8c54a5604d55bd8f638e85633130_a9efed --label 8a33c1 --workdir /github/workspace --rm -e INPUT_BRANCH -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/test-tiptap/test-tiptap":"/github/workspace" 8a33c1:7e2b8c54a5604d55bd8f638e85633130

• cd /github/workspace
  HEAD is now at dc2c971 Update README.md
• git branch refs/heads/main
• git config --global user.name 'github-actions[bot]'
• git config --global user.email 'github-actions[bot]@users.noreply.github.com'
• git reset --hard 'HEAD~1'
• git push --force
  error: src refspec refs/heads/main matches more than one
  error: failed to push some refs to 'https://github.com/xxxxxxxxxxxxx/cxxxxxxxxx'

Hi,

I have created an undo-push in GitHub action but it failed to do undo push. below the error logs.

Run exions/[email protected]
with:
branch: main
/usr/bin/docker run --name a33c17e2b8c54a5604d55bd8f638e85633130_a9efed --label 8a33c1 --workdir /github/workspace --rm -e INPUT_BRANCH -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e RUNNER_OS -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/test-tiptap/test-tiptap":"/github/workspace" 8a33c1:7e2b8c54a5604d55bd8f638e85633130

• cd /github/workspace
  HEAD is now at dc2c971 Update README.md
• git branch refs/heads/main
• git config --global user.name 'github-actions[bot]'
• git config --global user.email 'github-actions[bot]@users.noreply.github.com'
• git reset --hard 'HEAD~1'
• git push --force
  error: src refspec refs/heads/main matches more than one
  error: failed to push some refs to 'https://github.com/xxxxxxxxxx/xxxxxxxxxxxxxxx'

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

---

Missing package.json file.

A package.json file at the root of your project is required to release on npm.

Please follow the npm guideline to create a valid package.json file.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀