Skip to content

ci: dispatch docs bump to the renamed glassflow-docs repo - #43

Merged
PabloPardoGarcia merged 1 commit into
mainfrom
pablo/fix-docs-dispatch-rename
Aug 5, 2026
Merged

ci: dispatch docs bump to the renamed glassflow-docs repo#43
PabloPardoGarcia merged 1 commit into
mainfrom
pablo/fix-docs-dispatch-rename

Conversation

@PabloPardoGarcia

Copy link
Copy Markdown
Member

The docs repo was renamed argus-docs -> glassflow-docs yesterday (GLA2-310). repository_dispatch to the old name gets a 301, which curl --fail-with-body treats as success (it only fails on 4xx/5xx), so the v0.7.0 release's dispatch was silently dropped: the release job showed green while no bump PR appeared in the docs repo.

  • Points the dispatch URL (and comments) at glassflow/glassflow-docs.
  • The 0.7.0 catch-up has been triggered manually via the docs workflow's workflow_dispatch; the weekly schedule remains the safety net for any future lost dispatch.
  • DOCS_DISPATCH_TOKEN needs no change if it's a fine-grained PAT with the repo selected (repo selection follows renames); worth a glance if it was configured by name.

The docs repo was renamed argus-docs -> glassflow-docs (GLA2-310). The
GitHub API answers the old name with a 301, which curl --fail-with-body
treats as success (it only fails on 4xx/5xx), so the v0.7.0 dispatch was
dropped silently and no bump PR appeared. Point the dispatch at the new
name. The docs workflow's weekly schedule remains the fallback; the
0.7.0 catch-up was triggered manually via workflow_dispatch.
@PabloPardoGarcia
PabloPardoGarcia merged commit 4b680c8 into main Aug 5, 2026
8 checks passed
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