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
Backmerge with restoreWorkspace fails when no stash entry is found #55
Comments
saitho
added a commit
that referenced
this issue
Nov 27, 2023
Ignore "No stash entries found." when stashing is enabled but no files were actually stashed. Resolves: #55
saitho
added a commit
that referenced
this issue
Nov 27, 2023
Ignore "No stash entries found." when stashing is enabled but no files were actually stashed. Resolves: #55
Merged
saitho
added a commit
that referenced
this issue
Nov 27, 2023
Ignore "No stash entries found." when stashing is enabled but no files were actually stashed. Resolves: #55
saitho
added a commit
that referenced
this issue
Nov 27, 2023
Ignore "No stash entries found." when stashing is enabled but no files were actually stashed. Resolves: #55
github-actions bot
pushed a commit
that referenced
this issue
Nov 27, 2023
## [4.0.1](v4.0.0...v4.0.1) (2023-11-27) ### Bug Fixes * ignore empty stash ([d8e9734](d8e9734)), closes [#55](#55)
🎉 This issue has been resolved in version 4.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
If no stash entry is present, the
restoreWorkspace
(i.e.git stash pop
) fails.Expected Behavior
Backmerge plugin should ignore the error if no stash entry is found.
Steps To Reproduce
semantic-release
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: