Prettier fails
See original GitHub issueDescription
Prettier fails to format json file and commit it back, I think this is making it harder for people, and it should be helping
https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075
error: Your local changes to the following files would be overwritten by checkout:
[32](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:33)
data/Saurav-Pant.json
[33](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:34)
Please commit your changes or stash them before you switch branches.
[34](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:35)
Aborting
[35](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:36)
Error: Invalid status code: 1
[36](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:37)
at ChildProcess.<anonymous> (/home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v4/index.js:17:19)
[37](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:38)
at ChildProcess.emit (node:events:390:28)
[38](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:39)
at maybeClose (node:internal/child_process:1064:16)
[39](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:40)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5) {
[40](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:41)
code: 1
[41](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:42)
}
[42](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:43)
Error: Invalid status code: 1
[43](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:44)
at ChildProcess.<anonymous> (/home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v4/index.js:17:19)
[44](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:45)
at ChildProcess.emit (node:events:390:28)
[45](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:46)
at maybeClose (node:internal/child_process:1064:16)
[46](https://github.com/EddieHubCommunity/LinkFree/actions/runs/3700762171/jobs/6275926075#step:6:47)
at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
Screenshots
No response
Additional information
No response
Issue Analytics
- State:
- Created 9 months ago
- Comments:15 (14 by maintainers)
Top Results From Across the Web
Prettier fails in CI · Issue #79 · schuchard/prettier-schematic
Describe the bug In have installed the schematic and added script: npm run prettier script to my Azure Pipeline. It runs prettier -c...
Read more >How to overcome those prettier errors? - Stack Overflow
I am having similar issues with parsing errors with husky when trying to do a git commit. I "solved" it following this answer...
Read more >CLI - Prettier
Applying this practice will minimise the number of times the CI fails because of code formatting problems. If you need to pipe the...
Read more >prettier-eslint - npm
The problem. The fix feature of eslint is pretty great and can auto-format/fix much of your code according to your ESLint config. ·...
Read more >Formatting html files with prettier fails to insert spaces correctly
mach eslint --fix widget/tests/test_secure_input.html /Users/mark/dev/gecko/widget/tests/test_secure_input.html 52:3 error Insert `··` prettier/prettier ...
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
Do you have a test account that doesn’t have write access to the main LinkFree repo? If so, try testing with a fork on that account. I think some of your tests are working because your account has write access to both the fork and upstream repo.
If you look at the format action logs It only ran once. I think commits from an action won’t trigger the same action to re-run.