canonical / canonical/microcloud

Use MicroCeph tag for docs build

Open
#1,108 1 comment 0 reactions 0 assignees View on GitHub
Bug Documentation
Dominant language
Go
Stars
532
Forks
83
Avg merge
1d 14h
Merged PRs (30d)
36

Description

Currently we pin a specific commit on MicroCeph's `main` branch for the combined docs build. We should rather use the upstream https://github.com/canonical/microceph/releases/tag/v19.2.0%2Bsquid tag instead as it gets updated and will itself resolve to MicroCeph's standalone `stable` docs.

Contributor guide

Open the contributing guide

Research direction

Locate the configuration for the combined docs build and inspect how the MicroCeph main-branch commit is currently pinned. Change that source reference to the upstream v19.2.0+squid release tag, then run the repository's docs build to verify it resolves to the standalone stable docs and completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
build-system, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.