ci: point workflows at the reusable repo's canonical owner - #131
Merged
Conversation
The dart-actions repo moved from the btwld org to conceptadev. GitHub's REST API follows that rename redirect, so `gh api repos/btwld/dart-actions` still returns the repo and makes the reference look healthy. The Actions reusable-workflow resolver does not follow it: error parsing called workflow ... "btwld/dart-actions/..." : workflow was not found The reference is resolved at workflow load, so the whole file is rejected before any job is created. The run reports failure with zero jobs, no logs, and no annotation visible through the API -- only the web UI shows the cause. Both CI and publishing are affected here. The last CI run was 2026-08-05, before the move, so nothing has failed yet; the next push or release tag would have been the first to break. Inputs are unchanged: conceptadev/dart-actions still exposes ci.yml and publish.yml with the same workflow_call contract (flutter-version, run-dcm, secrets.token / packages_folder_path, packages). Comment wording matches the note already added to conceptadev/naked_ui, which hit this same trap. The btwld URLs in docs.yml are left alone: they are docs.page and raw.githubusercontent links, and line 37 asserts against a matching string in docs/llms.txt.mdx, so changing one without the other would break that check.
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.
Both CI and publishing are broken here
dart-actionsmoved from thebtwldorg toconceptadev. Two workflows still reference the old owner:ci.ymluses: btwld/dart-actions/.github/workflows/ci.yml@mainrelease.ymluses: btwld/dart-actions/.github/workflows/publish.yml@mainWhy it looks fine but isn't
gh api repos/btwld/dart-actionsstill returns the repo and its workflows, because the REST API follows rename redirects. That makes the reference look healthy under any manual check.The Actions reusable-workflow resolver does not follow redirects. The reference is resolved at workflow load, so the entire file is rejected before a single job is created:
The resulting run is confusing to diagnose: marked failed,
referenced_workflows: [], zero jobs, no logs, no annotation exposed through the API, and the run name falls back to the file path. Only the web UI shows the actual error.We hit exactly this in
conceptadev/mix— it silently blocked a release, and it took reading the run page in a browser to find. The comment wording added here matches the note already inconceptadev/naked_ui, which ran into the same trap.Not yet visible, but imminent
The last CI run here was 2026-08-05, before the move, so nothing has failed yet. The next push to
main, the next PR, or the next release tag would have been the first to break — and for a release, that fails after you've already pushed the tag.Safety
Pure owner rename; no input changes.
conceptadev/dart-actionsstill exposes bothci.ymlandpublish.ymlwith an unchangedworkflow_callcontract —flutter-version,run-dcm,secrets.tokenfor CI, andpackages_folder_path/packagesfor publish. Both files re-parse cleanly.This PR's own CI run is the verification: if it goes green, the reference resolves.
Deliberately not changed
docs.ymlalso mentionsbtwld, at lines 37 and 52 — but those aredocs.pageandraw.githubusercontentURLs, notuses:references, so they aren't affected by the resolver behavior. Line 37 also asserts against a matching string insidedocs/llms.txt.mdx, so changing one without the other would break that check. Worth a separate look if docs hosting needs repointing.