-
-
Notifications
You must be signed in to change notification settings - Fork 237
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
broken commit action with v4.7.0 #119
Comments
I can confirm that reverting to v4.6.0 will result in the action working as expected. |
Totally fine. Thanks for the fast reaction 🥇 |
Thanks for the fast reaction. I was looking for this issue this morning but I didn't expect that it would be closed already so I didn't see it. The moral of this story: Always specify patch version not just @v4 |
v4.7.1 is also breaking for me 😢 https://github.com/carlobadini/life/runs/1295722644?check_suite_focus=true |
The only difference I see between v4.6.0 and v4.7.1 is using "--" after branches in git operations: v4.6.0...v4.7.1. Is this something that could be causing it? |
Yeah. Totally forgot to add this change to the changelog (or revert it). The worrying thing for me right now is, that I can't reliably reproduce the error " I have to further read through the logs you all send me, but I think the culprit lies in the fact, that maybe Over the next few days I will build some sort of matrix with all possible trigger-combinations and will make sure to test every single one of those combinations. Not directly related to this issue, but the test suite which mocks |
That would be amazing! For the time being, do you think you can "hard" reset to v4.6.0 and release a new v4.7.2 (essentially making sure that the v4.6.0...v4.7.1 diff is only the |
@AnandChowdhary Just tagged v4.7.2 which reverts |
I have tested this and v4.7.2 works perfectly. Thanks! 😄 |
Version of the Action
v4.7.0
Describe the bug
With the latest release (4.7.0) I got this bug:
To Reproduce
My relevant action configuration
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Used Workflow
# Paste the Workflow you've used here
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: