tempo
tempo copied to clipboard
proposal: full docs → spec docs
See Slack thread
Problem
We are starting to see friction with hosting the docs in tempoxyz/tempo:
- harder to audit and/or bisect across commits (several docs commits infiltrating implementation commits)
- CI becomes a more complex
- increases our attack surface as we are exposed to a JS supply chain – GitHub Actions does have safeguards here, but who knows if GH Actions may have a vulnerability in the future and someone takes advantage of it against us.
- we will be encountering a previous friction we had where we will need to have code reviews on trivial docs commits (understand we need to have this requirement on this repo)
Solution
Only have the specs and reference implementation files in tempoxyz/tempo (under specs/**), and then call out to a tempoxyz/docs workflow to propose a PR to sync the specs.
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| tempo-docs | Dec 8, 2025 6:15am |