Repository navigation
Remove upstream's GitHub Actions workflows again - #231
Merged
Merged
Conversation
The clean-slate rebase onto v26.13.1 brought back the workflow files the fork had dropped, and renaming the default branch to main woke them up: upstream's "Test Shared libraries", nix-changes and friends trigger on pushes to main and canary, and they fail here because this fork is not built the way upstream's CI expects. Leaves the same three the node 16 stack keeps -- build-test.yml, build-test-branch.yml and release.yml, with the actions they use -- and drops the twelve upstream workflows plus the three actions and the CodeQL config that only they referenced. The fork's own CI runs on Buildkite (.buildkite/runtime-node-build-and-test.yml). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The clean-slate rebase onto v26.13.1 brought back the workflow files the fork had dropped, and renaming the default branch to main woke them up: upstream's "Test Shared libraries", nix-changes and friends trigger on pushes to main and canary, and they fail here because this fork is not built the way upstream's CI expects.
Leaves the same three the node 16 stack keeps -- build-test.yml, build-test-branch.yml and release.yml, with the actions they use -- and drops the twelve upstream workflows plus the three actions and the CodeQL config that only they referenced. The fork's own CI runs on Buildkite (.buildkite/runtime-node-build-and-test.yml).