feat: add extension favicon
Build / build (push) Successful in 10s

This commit is contained in:
2026-07-17 14:38:42 -05:00
parent c983ee2b1a
commit 8351fc65f5
6 changed files with 12 additions and 0 deletions
+1
View File
@@ -36,6 +36,7 @@ Use `.env.local` for local secrets. Keep `.env.local` and any real token-bearing
- `vite.config.ts` emits `dist/manifest.json` during production builds.
- `dist/` is the deployable output directory. Deployment or Chrome load-unpacked flows should point directly at `dist/`.
- `dist/` is generated output and should not be edited directly.
- Static extension assets live in `public/`; the current favicon source is `public/favicon.svg`.
- `npm run build` runs `scripts/verify-dist.mjs` after Vite to ensure the generated output has the required extension files.
- Host permissions are derived from `VITE_GITEA_BASE_URL`. Rebuild after changing the base URL.
- Runtime API calls are centralized in `src/api.ts`.