release fails at "git diff --ignore-space-at-eol --exit-code"
See original GitHub issueMy release fails at
Task "release" failed when executing "git diff --ignore-space-at-eol --exit-code"
Version is on 0.0.0 in package.json. I’m using shared runners on gitlab and following container jsii/superchain:1-buster-slim-node16
Anyone has an idea, what I could do?
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
[bug] TypescriptApp: Release task runs git diff in the ... - GitHub
This should be a fairly minor bug. Issue The release task runs this command: release | git diff --ignore-space-at-eol --exit-code However ...
Read more >git-diff Documentation - Git
NAME. git-diff - Show changes between commits, commit and working tree, etc ... This form implies --exit-code . git diff ... --ws-error-highlight=<kind>.
Read more >Git diff returns “Error: Process completed with exit code 1 ...
The right thing to do is continue-on-error when using github actions or ignore this status in other build systems. Share.
Read more >git diff with exit code 1 - Toshimaru's Blog
If there's a diff in git diff, I want the command to exit with an error.
Read more >Git diff Command – How to Compare Changes in Your Code
Perhaps you want to see the differences between two branches, commits, or files. These are common issues and tasks when working with a...
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 FreeTop 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
Top GitHub Comments
@pchaganti Check the output of the workflow. If there’s a diff it’s usually because your build is not stable (= a different result is produced when running
projen build
in the workflow compared to what is checked-in).@yanu23 Did you manage to resolve this? What was the issue in the end?