Skip to content

Doc infra to master - #544

Open
Becheler wants to merge 5 commits into
boostorg:masterfrom
Becheler:doc-to-master
Open

Doc infra to master#544
Becheler wants to merge 5 commits into
boostorg:masterfrom
Becheler:doc-to-master

Conversation

@Becheler

@Becheler Becheler commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

Before submitting

  • This PR targets the develop branch.
  • I searched for an existing PR or issue covering the same change.
  • My contribution is licensed under the Boost Software License 1.0.

Type of change

  • Bug fix
  • New feature or API addition
  • Refactor (no behavior change)
  • Documentation
  • Build, CI, or tooling
  • Other (specify below)

Does this PR introduce a breaking change?

  • Yes (describe migration impact below)
  • No

What this PR does

Cherry picks the commits that fixed the documentation deployment on develop so they apply on master for 1.92.

Motivation

It took me a long time to understand the ways that Boost deploys docs. When I understood that website-v2 boost bundle was bugged for our BGL case, I had to step back to imitate the Boost.Unordered deployment. It took some time and experimentations to make sure the doc infra was correctly wired:

This PR selects those changes by branching off master, cherry picking the relevant commits (git cherry-pick e61f290d 8286c075 cde7dbed c7836caf 1fd3ed4e) and applying them in order to avoid conflicts.

Testing

We will need the Boost.CI to run to verify:

  1. It passes green: https://app.circleci.com/pipelines/github/boostorg/boost
  2. The dashboard for beta 1.92 is here: https://www.boost.org/library/1.92.0.beta1/graph/
  3. Its link to its documentation renders: https://www.boost.org/doc/libs/1_92_0_beta1/doc/antora/graph/index.html/

Checklist

  • Existing tests pass (b2 in the test/ directory).
  • New behavior is covered by a test, or this is a docs / build / refactor change.
  • Documentation was updated if user-facing behavior changed.
  • No new compiler warnings on the platforms I built against.

@Becheler Becheler self-assigned this Jul 28, 2026
@Becheler Becheler added docs infra CI pipelines, build system (CMake/Jamfile), packaging and tooling. labels Jul 28, 2026
@cppalliance-bot

Copy link
Copy Markdown

An automated preview of the documentation is available at https://544.graph.prtest3.cppalliance.org/libs/graph/doc/html/index.html

If more commits are pushed to the pull request, the docs will rebuild at the same URL.

2026-07-28 10:23:12 UTC

@github-actions

Copy link
Copy Markdown

Compiler-warning counts vs develop (auto-generated).
PR run 30349935866 vs develop run 30257490643 (02817557ed).

Job Baseline After Delta
macos (clang, 14) 4 44 +40
macos (clang, 17) 4 44 +40
macos (clang, 20) 4 44 +40
ubuntu (clang-19, 14) 4 4 0
ubuntu (clang-19, 17) 4 4 0
ubuntu (clang-19, 20) 4 4 0
ubuntu (clang-19, 23) 4 4 0
ubuntu (gcc-14, 14) 10 10 0
ubuntu (gcc-14, 17) 10 10 0
ubuntu (gcc-14, 20) 10 10 0
ubuntu (gcc-14, 23) 10 10 0
windows_msvc_14_3 (msvc-14.3) 971 971 0

@Becheler
Becheler marked this pull request as ready for review July 28, 2026 10:44
@Becheler
Becheler requested a review from jeremy-murphy as a code owner July 28, 2026 10:44
@Becheler Becheler added the priority: high Blocks users or core functionality. Needs attention in the current cycle. label Jul 28, 2026
@jeremy-murphy

Copy link
Copy Markdown
Collaborator

Screenshot_20260728-211747.png
No it doesn't. 😅

@Becheler

Copy link
Copy Markdown
Collaborator Author

Oh my !
Apologies, it DOES absolutely target the master branch 🤦🏽

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs infra CI pipelines, build system (CMake/Jamfile), packaging and tooling. priority: high Blocks users or core functionality. Needs attention in the current cycle.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants