| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This PR improves the pr-checks workflow by ensuring all checks run even if one fails and adds helpful diff summaries to job outputs when there are changes to JS bundles or generated workflows.
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .github/workflows/pr-checks.yml | Adds if: always() conditions to ensure all workflow steps run |
| .github/workflows/script/check-js.sh | Adds JS diff output to step summary and resets bundled files |
| .github/workflows/script/verify-pr-checks.sh | Adds generated workflows diff output to step summary |
Sorry, something went wrong.
| git diff --output="$RUNNER_TEMP/js.diff" | ||
| cat "$RUNNER_TEMP/js.diff" >> $GITHUB_STEP_SUMMARY |
There was a problem hiding this comment.
Consider uploading the diff as an artifact
Sorry, something went wrong.
There was a problem hiding this comment.
I initially had that, but thought this was nicer because you can see the syntax-highlighted diff without having to download a file, unpack it, and open it.
Sorry, something went wrong.
There was a problem hiding this comment.
I think both are nice in case there's a big diff. But this is a very minor comment, good to go as is.
Sorry, something went wrong.
There was a problem hiding this comment.
Let's leave it for now then, but we can add it later if we find it's needed?
Sorry, something went wrong.
| git diff --output="$RUNNER_TEMP/workflows.diff" | ||
| cat "$RUNNER_TEMP/workflows.diff" >> $GITHUB_STEP_SUMMARY |
There was a problem hiding this comment.
Ditto here
Sorry, something went wrong.
|
A common gotcha is having out of date dependencies locally. We could consider posting a comment on the PR with the command to run (e.g. npm i && npm run build && npm test && npm run lint). We could also consider integrating a check that dependenices are up to date as part of the build process, if this is possible to do quickly. |
Sorry, something went wrong.
|
I'm not super keen on running npm i as part of npm run build just because of how slow it is, but this is also something we could consider. |
Sorry, something went wrong.
|
Agreed on both points. I don't think we should run npm install as part of anything we do frequently during normal development. I'll have a look at what we can do to detect whether npm install has to be run, but separately from this PR. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Improves the pr-checks workflow so that:
Risk assessment
For internal use only. Please select the risk level of this change:
Merge / deployment checklist