breaking: move dispatch-and-wait into its own sub-directory #1

New issue

Closed

opened 2026-10-25 17:25:20 +00:00 by Gilles · 0 comments

Gilles commented

2026-10-25 17:25:20 +00:00

Owner

dispatch-and-wait currently lives at the repo root while its sibling report-status lives in report-status/ -- inconsistent, and it means the repo root can't host a third action later without ambiguity about which one @v1 on its own means. Move it to dispatch-and-wait/ so both actions are referenced the same way: uses: .../guardians_of_the_galaxy/actions/dispatch-and-wait@v1 and .../report-status@v1.

Breaking for the one caller that exists so far (Filao/backend's PR #36, not yet merged) -- update its uses: path in the same change.

dispatch-and-wait currently lives at the repo root while its sibling report-status lives in report-status/ -- inconsistent, and it means the repo root can't host a third action later without ambiguity about which one `@v1` on its own means. Move it to dispatch-and-wait/ so both actions are referenced the same way: `uses: .../guardians_of_the_galaxy/actions/dispatch-and-wait@v1` and `.../report-status@v1`. Breaking for the one caller that exists so far (Filao/backend's PR #36, not yet merged) -- update its `uses:` path in the same change.

Gilles added the

breaking

label

2026-10-25 17:25:20 +00:00

Gilles referenced this issue from a commit

2026-10-25 17:26:56 +00:00

breaking: move dispatch-and-wait into its own sub-directory

Gilles referenced this issue from a pull request that will close it,

2026-10-25 17:27:03 +00:00

breaking: move dispatch-and-wait into its own sub-directory #2

Gilles closed this issue

2026-10-25 17:31:34 +00:00