Stop building the CodeQL for VS Code docs now they've been migrated #16496
Conversation
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
|
It turns out that we need to update all the links to the VS Code extension before we can stop generating the files as part of the Sphinx build, see: https://github.com/github/semmle-code/actions/runs/9092490831/job/24989320159. |
felicitymay
added
the
ready-for-doc-review
subatoi
approved these changes
May 15, 2024
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.
This change should stop us building the CodeQL for VS Code docs as part of the docs publication for the CodeQL docs site. It's likely to delete the HTML files from the
codeql-docsrepository, but I've checked with Rachael and this won't have any impact on the redirects that we already have in place.This change is worth doing so that, as we hand over more responsibility for the CodeQL docs site to the CodeQL team, there are fewer areas for confusion.
I'll test this PR by running a docs build and creating a test PR to update the CodeQL docs site.