ci: dispatch docs bump to the renamed glassflow-docs repo - #43
Merged
Conversation
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.
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.
The docs repo was renamed
argus-docs->glassflow-docsyesterday (GLA2-310).repository_dispatchto the old name gets a 301, whichcurl --fail-with-bodytreats 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.glassflow/glassflow-docs.workflow_dispatch; the weekly schedule remains the safety net for any future lost dispatch.DOCS_DISPATCH_TOKENneeds 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.