You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1 configuration not found
Warning: Code scanning cannot determine the alerts introduced by this pull request, because 1 configuration present on refs/heads/main was not found:
Actions workflow (python-code-quality.yml)
❓ .github/workflows/python-code-quality.yml:python-checks/bandit-version:1.7.8/black-version:23.1.0/flake8-version:3.9.2/min-python-version:3.7/os:ubuntu-22.04/pylint-version:2.12.2/python-version:3.10
I see where it comes from. A similar thing happened for CodeQL when we adjusted the languages names. Since the strategy matrix values are used to generate the configuration slug, changing any strategy matrix will create a different configuration.
Here, it's because it still expects results from the configuration that had the old black version like before.
The way out:
in GitHub security scanning tab, delete the old configuration. This will solve for this time.
Or
Change the strategy matrix values with tool versions to job-level or workflow-level env vars instead. We will probably need to adjust the required status checks to the new name of the check if it used that job, and that would be a good thing.
I don't see anything in the security tab for the name of the configuration or a button to delete it. I see links to the workflow. Rest is read-only. Screenshots attached. Let me know if there is anything I can explore more.
Since #3799, this shouldn't happen with this workflow, until the matrix strategy is changed, like when the runner OS will change to Ubuntu 24.04. Otherwise I can always go and "delete" the old configuration (just the key/label) when only the new one is uploading results.
Describe the bug
This just came to my attention while checking open PRs:
Actions workflow (python-code-quality.yml) complains about:
See e.g.:
#3671
--> https://github.com/OSGeo/grass/runs/24278615418
If this is known/expected just close this report.
The text was updated successfully, but these errors were encountered: