Skip to content

Publish docs/ to b3pay.net from this repository - #17

Merged
b3hr4d merged 1 commit into
mainfrom
claude/project-thread-vsgh2j
Oct 31, 2026
Merged

b3hr4d merged 1 commit into
mainfrom
claude/project-thread-vsgh2j

Conversation

@b3hr4d

@b3hr4d b3hr4d commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

What this does

b3pay.net serves these docs at https://b3pay.net/docs/b3note/. Until now it built them from a pinned commit of this repository (7225d27), with a manifest kept in b3pay.net (modules/hosted/b3note.json). This PR makes B3Note publish them itself:

  • b3pay-module.json: the same manifest b3pay.net used, so the pages don't change. The four pages of docs/ become How it works (the home page), Development, Operations and What changed in v2.
  • .github/workflows/b3pay-site.yml ("Docs on b3pay.net"): calls b3pay.net's reusable publish-module.yml, pinned to b3pay.net's main commit 07de4cd.
    • On a pull request that changes docs/, the manifest or the workflow, it builds the module with b3pay.net's tools, then builds the whole site with it and checks the site's links. A page that would break b3pay.net fails here.
    • On a push to main that changes them, it also commits the built module to this repository's b3pay-site branch and calls the deploy hook, if there is one.
    • It never writes to b3pay.net. The publish job has contents: write on this repository only.
  • README: says where the pages are served and how they get there.

Verified

I built the module with b3pay.net main's tools from this branch (build-module.mjs --source ../B3Note), built the whole site with it, and checked the links:

module  b3note: 4 pages, 0 static files
· All internal links are valid. ·
links  20002 links into the site reach a page, file or function (119 pages; 1032 external links not followed)

After merging

  1. The merge itself runs the workflow on main, because it adds the manifest and the workflow, and that first run creates the b3pay-site branch. If a ruleset blocks new branches or pushes from GitHub Actions, that branch needs an exception.
  2. A b3pay.net PR then switches the registry entry to { "repo": "B3Pay/B3Note", "branch": "b3pay-site" } and removes modules/hosted/b3note.json.
  3. Optional: the organization secret B3PAY_SITE_DEPLOY_HOOK makes the site rebuild right after a publish. Without it, the change goes live with the site's next deploy.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WnX8bdtbRqZMtdj8oTZjpX

b3pay.net serves these pages at /docs/b3note/, built until now from a
pinned commit of this repository with a manifest kept in b3pay.net. With
b3pay-module.json and the "Docs on b3pay.net" workflow, the repository
publishes them itself: a pull request that changes docs/ builds the module
and the whole site with it, and a push to main commits the built module to
the b3pay-site branch, which b3pay.net will read once its registry points
there. The manifest is the one b3pay.net used, so the pages do not change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WnX8bdtbRqZMtdj8oTZjpX
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-30T22:30:49.470503Z 4405d80 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@b3hr4d
b3hr4d merged commit 7b3344e into main Oct 31, 2026
4 checks passed
b3hr4d pushed a commit to B3Pay/b3pay.net that referenced this pull request Oct 31, 2026
B3Pay/B3Note#17 merged, and its first run on main published B3Note's docs
module to that repository's b3pay-site branch (fabb0a2, built from
7b3344e). The registry reads that branch, as it does IC Reactor's and
Meant's, instead of building commit 7225d27 with modules/hosted/b3note.json,
which is removed, with its line in the manifest test. modules/README.md
names modules/hosted/ instead of linking it, since the folder is now empty
and git keeps no empty folder.

B3Note's built pages are the same as before, byte for byte. The changelog
dates the B3Forge guides of #19 2026-10-31, the day they merged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WnX8bdtbRqZMtdj8oTZjpX
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants