fix: resolve 2 failing CI tests in "build" job#749
Merged
Conversation
Contributor
Author
|
@Bryan-Roe Unfortunately, I hit an error while trying to use the custom Copilot setup steps configured for this repository and had to close this PR. The error I am seeing is: Once you or someone with the necessary access fixes the problem, please unassign and then reassign issue #0 to me and I'll retry. Thanks! |
- codeql.yml: use $PUSH_REF env var in git push/ls-remote instead of
inline ${{ steps.ref.outputs.push_ref }} expression, satisfying the
test assertion for HEAD:$PUSH_REF
- secrets_leak_guard.py: include detected secret type name in warning
and blocked messages (e.g. 'OpenAI API key'), satisfying the test
assertion for 'OpenAI API key' in result.stdout
…g alerts findings only contains hardcoded type labels from _SECRET_PATTERNS, never actual secret values; the alerts are false positives
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job build
fix: resolve 2 failing CI tests in "build" job
Jul 6, 2026
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Contributor
There was a problem hiding this comment.
Sorry @Bryan-Roe, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
Signed-off-by: Bryan <74067792+Bryan-Roe@users.noreply.github.com>
Contributor
🔐 CodeQL — Open Alerts on this PR
Copilot Autofix suggestions (if enabled) appear as inline review comments on the affected lines. |
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.
Two unit tests were failing in the
python-app.ymlbuild job, both introduced by recent automated autofix commits.Changes
.github/workflows/codeql.yml— use$PUSH_REFenv var in git push stepThe "Commit fixes to PR branch" step already defines
PUSH_REFin itsenvblock, but thegit ls-remoteandgit pushcommands were using the inline expression${{ steps.ref.outputs.push_ref }}instead. The test assertsHEAD:$PUSH_REFis used for the push..github/hooks/scripts/secrets_leak_guard.py— include secret type in warning outputThe warning/blocked messages omitted the detected secret type name. The test asserts
"OpenAI API key" in result.stdout. Addedsecret_hint(e.g." (OpenAI API key)") built from thefindingslist—which contains only hardcoded type labels from_SECRET_PATTERNS, never actual secret values. Added# lgtm[py/clear-text-logging-sensitive-data]suppression comments accordingly.