Repository navigation
chore: drop the unused docs image build - #53
Conversation
The docs are served by the centralized docs.txpipe.io site (txpipe/docs), which pulls this repository as a submodule and builds the content itself. Nothing deploys ghcr.io/txpipe/boros-docs, so the docs Dockerfile and the workflow that publishes it on every push to main are dead weight. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Removes
docs/Dockerfileand itsdocs/.dockerignoreand.github/workflows/docs.yml, which build and pushghcr.io/txpipe/boros-docs:<sha>on pushes tomain.Nothing deploys that image. The boros docs are served by the centralized docs.txpipe.io site (txpipe/docs), which pulls this repository as a submodule and builds the content itself;
boros.txpipe.ioredirects tohttps://docs.txpipe.io/boros. The docs sources underdocs/stay.🤖 Generated with Claude Code
Summary by CodeRabbit