Always run the latest
tools PR checks so we can make them required
#699
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 change runs integration tests with all three bundles, even if
tools: latest
would be the same astools: null
(i.e. omitting thetools
property). This allows us to make integration tests against each one of these threetools
configurations required status checks on PRs.As future work, we could move the
"$CODEQL_VERSION_DEFAULT" == "$CODEQL_VERSION_LATEST"
logic into jobs running withtools: latest
to minimise redundant work, or investigate depending on statuses rather than Actions jobs. However right now the additional cost created by these redundant jobs doesn't seem to justify the complexity.Merge / deployment checklist