Action sometimes fails on push
See original GitHub issueThanks a lot for this amazing action! We use it at CrownLabs@Polito
We had some action (1, 2) failing on pushes, this is the log (same on both):
Run dorny/paths-filter@v2.0.0
with:
filters: webservice:
- 'webservice/**/*'
token: ***
/usr/bin/git fetch --depth=1 origin 0000000000000000000000000000000000000000
fatal: remote error: upload-pack: not our ref 0000000000000000000000000000000000000000
fatal: the remote end hung up unexpectedly
##[error]The process '/usr/bin/git' failed with exit code 128
This is our action implementation. Can you tell us if we are doing something wrong
Thank you very much!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Error in git push github actions · Discussion #25710 · community
I was using github actions to run my code to generate graphs and push them. It works inconsistently. Sometimes it works, sometimes it...
Read more >GitHub Action workflow not running - Stack Overflow
Whenever you add a new workflow, sometimes it may happen that workflow may not get into the running phase even after everything is...
Read more >Skipping workflows on a push to the main branch - YouTube
Did you know that you can use keywords to skip a GitHub Action workflow, so that it doesn't trigger? This video will show...
Read more >Push notifications stopped being d… | Apple Developer Forums
The problem is that push notifications have stopped working (delivery of notifications to devices) in production sometime during the first week of May...
Read more >Force Push in Git - Everything You Need to Know | Tower Blog
Whenever you run the git push command, Git has a look at your local repository and copies to the remote side whatever is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same here. Would be nice to have. If check diffs between commits, then the next commit may not cover all the tests of the previous one, but CI will write that everything went well, which will be very dangerous.
This is great Thank you very much!