fix(codeql): use proper tagged version #256
Closed
Conversation
This file contains 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
iainlane
changed the title
We set this up by using GitHub's wizard in the UI. Looks like it configured it with a random commit (HEAD at the time maybe) and not one that was tagged. Here we update to [the nearest tag][tag] which [contains][contains] the [commit we previously had][commit]. This should hopefully unblock automated updates. [commit]: github/codeql-action@9550da9 [contains]: https://github.com/github/codeql-action/commits/366cd9811409649a3e1276ce7f1a1c9023832b56/ [tag]: https://github.com/github/codeql-action/releases/tag/v2.25.7
iainlane
force-pushed
the
iainlane/fix-codeql-tag-with-bump
branch
from
3de7405
to
55ca68f
Compare
zerok
approved these changes
Sep 20, 2024
|
Renovate did actually manage to update codeql in a2a8967, so this PR isn't needed 😁 |
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.
We set this up by using GitHub's wizard in the UI. Looks like it configured it with a random commit (HEAD at the time maybe) and not one that was tagged. Here we update to the nearest tag which contains the commit we previously had.
This should hopefully unblock automated updates.