Skip to content

ci: drop the PR builds that have never worked in this fork - #3

Merged
vibesoftwarecoder merged 1 commit into
masterfrom
ci/trim-pr-pipeline
Sep 10, 2026
Merged

ci: drop the PR builds that have never worked in this fork#3
vibesoftwarecoder merged 1 commit into
masterfrom
ci/trim-pr-pipeline

Conversation

@vibesoftwarecoder

Copy link
Copy Markdown
Owner

build.yml has failed on every run since 2026-05-01 — nine consecutive failures before any of today's work existed. A permanently red check gates nothing and teaches people to ignore CI, which is how the next real failure gets missed.

What was actually broken

job state notes
setup
build-appimage a real Qt 6 build
build-steamlink has never linked in this fork
build-win-mac ⚠️ passes on macOS, fails on Windows

Neither failing job is load-bearing. The builds that actually ship are build-moonlightvibe-windows.yml and -mac.yml, which run on push to master and are green.

So build.yml keeps the two jobs that pass, and build-steamlink.yml / build-win-mac.yml are deleted — build.yml was their only caller.

Not deleted outright, deliberately

The first instinct was to delete build.yml entirely. That would have been a mistake: its build-appimage / build and setup are master's required status checks, so removing it would leave branch protection waiting forever on checks that no longer exist.

That is precisely the deadlock fixed an hour ago, where the required context build was never produced by any PR workflow and no pull request could merge at all.

Cost, stated plainly

PR coverage is now Linux-only. A Windows-specific break will pass the PR and fail on the master push instead. Trimming build-win-mac also gives up a working macOS PR build.

That is a real reduction, accepted deliberately over leaving a red check nobody reads. Repairing the Windows PR build is the better fix if it is ever worth the time.

🤖 Generated with Claude Code

https://claude.ai/code/session_01SQvL62WkT8xDWXqyjFCGDw

build.yml has failed on every run since 2026-05-01 -- nine consecutive
failures before any of today's work existed. A check that is permanently red
gates nothing and teaches people to ignore CI, which is how the next real
failure gets missed.

build-steamlink has never linked here, and build-win-mac fails on Windows
while passing on macOS. Neither is load-bearing: the builds that actually ship
are build-moonlightvibe-windows.yml and -mac.yml, which run on push to master
and are green.

So build.yml keeps the two jobs that pass -- setup and build-appimage, a real
Qt 6 build -- and build-steamlink.yml and build-win-mac.yml are deleted, since
build.yml was their only caller.

⚠️ PR coverage is now Linux-only. A Windows-specific break will pass the PR
and fail on the master push instead. That is a real reduction, accepted
deliberately over leaving a red check nobody reads; repairing the Windows PR
build is the better fix if it is ever worth the time.

⛔ build.yml is NOT deleted outright, which was the first instinct. Its
`build-appimage / build` and `setup` are master's required status checks, so
removing it would leave protection waiting forever on checks that no longer
exist -- exactly the deadlock fixed an hour ago, where the required context
"build" was never produced by any PR workflow.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SQvL62WkT8xDWXqyjFCGDw
@vibesoftwarecoder
vibesoftwarecoder merged commit 1c5f539 into master Sep 10, 2026
2 checks passed
@vibesoftwarecoder
vibesoftwarecoder deleted the ci/trim-pr-pipeline branch September 10, 2026 15:09
@vibesoftwarecoder vibesoftwarecoder mentioned this pull request Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant