Skip to content

fix(ci): skip upstream release jobs on fork - #6

Merged
internetisalie merged 3 commits into
devfrom
fork-ci-upstream-guards
Sep 25, 2026
Merged

internetisalie merged 3 commits into
devfrom
fork-ci-upstream-guards

Conversation

@internetisalie

@internetisalie internetisalie commented Sep 25, 2026 •

Copy link
Copy Markdown
Owner

Issue for this PR

Closes #5

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

The fork's dev push leaves generate queued on an unavailable Blacksmith runner. The publish job also queues because its always() condition runs after the upstream-only build jobs are skipped. Opening an issue or PR queues upstream triage and duplicate-check jobs on the same unavailable runner. This PR limits those jobs and the GitHub Action release job to anomalyco/opencode. On the fork, they skip before requesting a runner. Upstream behavior is unchanged.

How did you verify your code works?

  • Parsed the three workflow files and checked the diff for whitespace errors.
  • Confirmed the merged fork dev run has generate and publish queued on Blacksmith, while Linux tests, typecheck, and Nix evaluation use GitHub runners.
  • The PR checks will verify that the new conditions are accepted by GitHub Actions.

Screenshots / recordings

No UI change.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

@internetisalie
internetisalie merged commit 2648652 into dev Sep 25, 2026
8 checks passed
@internetisalie
internetisalie deleted the fork-ci-upstream-guards branch October 3, 2026 23:51
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.

Fork dev CI queues upstream generation and publishing jobs

1 participant