mirror of
https://github.com/ZTatman/myst.git
synced 2026-11-20 20:07:59 +00:00
No description
| docs/plans | ||
| packages | ||
| .gitignore | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| README.md | ||
| tsconfig.base.json | ||
| tsconfig.json | ||
Embargo
Your code, under embargo.
Embargo is a companion service for Forgejo that lets repo owners create expiring, revocable, read-only share links for private code snapshots.
Phase 1 PR Breakdown
Phase 1 is split into these reviewable branches:
codex/phase1-bootstrap-monorepocodex/phase1-cli-init-skeletoncodex/phase1-service-foundationcodex/phase1-forgejo-integrationcodex/phase1-grants-viewercodex/phase1-dashboard-logs-settings
Core Principles
- Embargo runs beside Forgejo and talks to it only through the Forgejo API.
- Share links pin to an immutable
commit_sha, not a moving branch. - Embargo uses its own owner auth for MVP.
- Forgejo access is performed by a constrained service account with minimum PAT scopes.
- A repo is shareable only if the service account can see it and Embargo has sharing enabled for it.
Current CLI Surface
pnpm --filter @embargo/cli build
node packages/cli/dist/index.js init --dir ./embargo
node packages/cli/dist/index.js status --dir ./embargo
node packages/cli/dist/index.js start --dir ./embargo
node packages/cli/dist/index.js stop --dir ./embargo
The Phase 1 pull requests are intentionally stacked so each review focuses on one layer of the system at a time.