repo: revert fork-only tooling commits that leaked in via #1426 - #1439
Merged
harshithmohan merged 3 commits intoSep 14, 2026
Merged
Conversation
Contributor
Author
|
This PR is at everyone else's discretion,. Although might provide some auto updates, it is rather noisy |
|
Member
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
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.




Summary
workflow_dispatchtrigger + action version bump) that were never meant for this repo — they belong to my fork's own CI, not upstreammasteras a side effect of merging fix(abstractions): make LanguageExtensions unknown-language tracking thread-safe #1426: that fix branch was accidentally cut from my fork'smasterafter I'd pushed the tooling commits there, so they rode along in the mergeWhat's reverted
Add Dependabot and CodeQL to fork toolingAdd workflow_dispatch trigger to CodeQLrepo(workflows): bump codeql-action to v4