tamada / sibling

93%

main: 93%

LAST BUILD ON BRANCH refactor/reusable-workflows

branch: refactor/reusable-workflows

CHANGE BRANCH

x

Reset

• refactor/reusable-workflows
• bugs/panicked_in_specifying_dir
• ci/deploy-page
• fix/publish-site-build
• golang
• introduce_github_actions
• main
• release/v1.1.0
• release/v1.1.0-beta1
• release/v1.1.0-beta2
• release/v1.1.1
• release/v1.1.2
• release/v1.1.3
• release/v1.1.4
• release/v1.2.0
• release/v1.2.1
• release/v1.2.2
• release/v1.2.3
• release/v1.2.4
• release/v1.3.0
• release/v2.0.0-beta-1
• release/v2.0.0-beta-2
• release/v2.0.0-beta-3
• release/v2.0.0-beta-4
• release/v2.0.0-beta-5
• release/v2.0.0-beta-6
• release/v2.0.0-beta-7
• release/v2.0.1
• release/v2.0.2
• release/v2.0.3
• release/v2.0.4
• release/v2.0.5
• release/v3.0.0
• reorganize_structure
• rust
• separate_cli_and_lib
• sibling2

Build # 31152033634

Build Type

Pull #48

github

Committed by tamada

Commit Message

ci: release through the reusable workflows of tamada/.github

The publish workflow did the tagging, the release, and the site deployment by
itself. Hand them to the reusable workflows, and keep here what only this
repository knows; building the command for each platform, and publishing the
crate.

- release-start tags main and opens the release as a draft,
- build-hugo-and-publish builds docs and deploys it to Pages, and
- release-finish takes the draft off with the token of the GitHub App.

The draft matters. The assets are attached while nobody knows about the
release, and the last job publishes it, which fires `release: published`;
the release published by GITHUB_TOKEN, as the old workflow did, fires nothing.
That is why notify-publish.yaml has never run once, and it will from now on.

The site deployment was broken in a quiet way. The Pages of this repository
serves what a workflow uploads (build_type: workflow), while the workflow
pushed the built site to the gh-pages branch; the job succeeded, the branch
moved, and Pages served the older site. It still tells v2.0.5 today, after the
release of v3.0.0. build-hugo-and-publish uploads the artifact to Pages, hence,
the deployment reaches the site.

Also quiet the shellcheck of versionup.yaml; the redirections were unquoted,
and it read a header into a variable which nothing used.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Pull Request Pull Request #48: Release through the reusable workflows of tamada/.github

Coverage Stats

1065 of 1149 relevant lines covered (92.69%)

12.42 hits per line