| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
This makes it easier to find the job that produced the status.
There was a problem hiding this comment.
This PR adds job identification metadata to the overlay analysis status file stored in the GitHub Actions cache. When an overlay-base analysis fails to complete, the action now records the workflow run ID, run attempt number, and job name alongside the failure status, making it easier to trace which job produced the status.
Changes:
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/overlay/status.ts | Defines JobInfo interface, adds optional job field to OverlayStatus, adds createOverlayStatus factory |
| src/init-action-post-helper.ts | Uses new createOverlayStatus helper when recording overlay failure status |
| src/init-action-post-helper.test.ts | Sets GITHUB_RUN_ID, GITHUB_RUN_ATTEMPT, GITHUB_JOB env vars and asserts job info in saved status |
| lib/init-action-post.js | Auto-generated JS reflecting the TS source changes (not reviewed per convention) |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good. Just one small suggestion, but it's not really specific to this PR and would be out-of-place as a change here.
Sorry, something went wrong.
| process.env["GITHUB_REPOSITORY"] = "github/codeql-action-fake-repository"; | ||
| process.env["GITHUB_RUN_ID"] = "12345"; | ||
| process.env["GITHUB_RUN_ATTEMPT"] = "1"; | ||
| process.env["GITHUB_JOB"] = "analyze"; | ||
| process.env["RUNNER_TEMP"] = tmpDir; |
There was a problem hiding this comment.
Minor: It might be nice to extend setupActionsVars with all environment variables that we'd typically expect in an Actions environment and modify it to accept an argument with a (partial) mapping of specific environment variables we want to set. Not necessarily something for this PR.
Sorry, something went wrong.
There was a problem hiding this comment.
Good idea. I'll take a look at this in a separate PR.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This makes it easier to find the job that produced the status.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
Products:
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist