Fix/code scanning workflow dispatch#160
Open
Flipmonster wants to merge 3 commits intoadvanced-security:mainfrom
Open
Fix/code scanning workflow dispatch#160Flipmonster wants to merge 3 commits intoadvanced-security:mainfrom
Flipmonster wants to merge 3 commits intoadvanced-security:mainfrom
Conversation
- Enhanced PR reference handling to better support workflow_dispatch events - Added better debug logging for reference handling - Modified getAlertsInPR to try head ref before merge ref - Fixed property access on CodeAlert objects - Added PR head branch detection from PR info This change improves how code scanning analyses are retrieved when triggered by workflow_dispatch events, particularly in the context of pull requests. It adds more robust reference handling and better debugging capabilities.
Contributor
There was a problem hiding this comment.
PR Overview
This PR improves the retrieval logic for code scanning analyses when triggered by workflow_dispatch events in pull request contexts. Key changes include enhanced PR reference handling by trying multiple refs, improved debug logging, and standardized property access on CodeAlert objects.
Reviewed Changes
| File | Description |
|---|---|
| ghascompliance/checks.py | Updated logic for retrieving code scanning alerts with multiple refs and improved error/debug logging |
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
ghascompliance/checks.py:105
- The refs_to_try list starts with the merge ref, but the PR description indicates that the head ref should be tried first. Consider reordering the list so that the head ref is attempted before the merge ref.
f"refs/pull/{GitHub.repository.getPullRequestNumber()}/merge",
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR improves how code scanning analyses are retrieved when triggered by
workflow_dispatchevents, particularly in the context ofpull requests.Changes include enhanced PR reference handling, better debug logging, and improved property access on CodeAlert objects. The changes ensure that both head and merge refs are tried in the correct order, providing better support for
workflow_dispatchevents in pull request contexts.This occurs because during workflow_dispatch events, the reference handling wasn't properly considering the PR context, leading to failed analysis retrieval.
overview
This fix ensures that code scanning analyses are properly retrieved during workflow_dispatch events in pull requests, which is particularly important for:
The changes maintain backward compatibility while improving the robustness of the code scanning analysis retrieval process.
Testing
The changes have been tested with:
Documentation
For more information about the code scanning API endpoints being used, see:
https://docs.github.com/en/enterprise-cloud@latest/rest/code-scanning#list-code-scanning-analyses-for-a-repository
Reopening here as well since there are some other changes - After playing around with a few different setups.