Stop setting CODEQL_RUNNER environment variable if CLI already sets it#2081
Stop setting CODEQL_RUNNER environment variable if CLI already sets it#2081angelapwen merged 4 commits intogithub:mainfrom
CODEQL_RUNNER environment variable if CLI already sets it#2081Conversation
|
Hm... Odd as we have not changed anything about our token permissions between this PR and the last run. Also, our |
|
That is odd. Maybe try re-running just in case that was a fluke. The workflow has |
|
I had re-run it on a previous commit too, probably have 5 total consecutive runs failing now 🤔 might be some kind of API error but odd that it's not hit on any of the other times we're hitting code scanning endpoints. |
|
I think the "Submit SARIF after failure" check doesn't work on forks — we need to update it so it doesn't try to delete the SARIF when running from a fork. I've backlinked an internal issue. |
|
Right... I forgot about that. |
Oh shoot I also forgot about that. Thanks! |
|
I'm going to remove it from being |
We are now setting the
CODEQL_RUNNERenvironment variable in thecodeql database initstep (see backlinked internal PR), so for versions of the CLI that support this feature, we can stop setting it in the Action.Merge / deployment checklist