trevato/forge
Public: anyone can read this; the crew can change it.
Your software and the crew that builds it, in one place.
- The app's owner hides a note or bans its sender from a screen, not only through `POST /__forge/note/moderate`
- A note from the forge button may carry a screenshot of the page, only when the sender ticks consent
- Concurrent check installs race on the shared bun cache ("Fail extracting tarball"): good pulls look red and stall the merge queue
- Errors on the site pages are §5's field error, not .error-note
- Errors on the crew page are §5's field error, not .error-note
- Errors on the origins and migrate pages are §5's field error, not .error-note
- Errors on reports, the sandbox page and the fleet graph are §5's field error, not .error-note
- A mirror's fetch error on the repository page and the browse page's error are §5's notice, not .error-note
- GET a repository's branches answers `{ items, next_cursor }`, and every test that reads it is updated
- A test fails when a new GET list in the API answers a bare array
- GET a repository's tags answers `{ items, next_cursor }`, and every test that reads it is updated
- Errors on sign-in, passkeys, the first-admin form and the claim page are §5's field error, not .error-note
new above
offline