Repository navigation
ci: release-please dispatches Docs on the tag it creates - #47
Merged
Merged
Conversation
A tag pushed with GITHUB_TOKEN starts no workflow, so Docs' push: tags trigger never fires for a release-please release. The release-please job now runs docs.yml on the new tag, where the deploy job publishes to Pages. The docs.yml header says Pages is on instead of asking for it. Done: the next release publishes its docs without a manual re-run. Next: the libhdf5 zips in #32. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the org release app (#37) the tag starts Docs by itself, so the dispatch runs only without it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Requested by Paul
Closes #12: its last gap was docs for a release whose tag starts no workflow.
GITHUB_TOKEN, and a tag pushed that way starts no workflow, so that release would publish no docs. On that path the job now dispatchesdocs.ymlon the new tag (release_created/tag_name).github.refis thenrefs/tags/<version>, so the deploy job runs, and thegithub-pagesenvironment's*.*.*rule allows it. This mirrors ci: open Release PRs with the org release app when set up #37's CI dispatch fallback.docs.ymlheader now says Pages is on instead of asking for it to be enabled.What else #12 asked for is already done:
*.*.*tag rule ongithub-pages, the same setup as the other five kits. The 0.11.0 tag (the newest) built and deployed, and https://mac4dstem.github.io/FormatoKit/documentation/ is live. Paul does not need to click anything.macos-26) for CI and Docs, pages permissions at job level, every product in the consumer check, thexcframework-urljob: ci: one pinned Xcode, macOS only, every product in the consumer check #28.._*entries and thecodesign --strictcheck: Rebuild the libhdf5 xcframework zips without AppleDouble entries and verify codesign --strict #32.Fixes #12
🤖 Generated with Claude Code