You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/copilot-instructions.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,8 +34,8 @@
34
34
- Async/await misuse or blocking operations in async contexts
35
35
- Improper trait implementations
36
36
37
-
### No Prerelease Docs
38
-
-If the PR contains both code changes to features/functionality AND updates in `/documentation`: Documentation updates must be separated to keep public docs in sync with released versions. Either mark new topics with `unlisted: true` or remove/hide the documentation.
37
+
### No Doc Updates with Code Changes
38
+
-PRs with code changes shouldn't update `/documentation` - docs deploy on merge, code on release. Use `unlisted: true` or remove/hide docs.
2.**Bundle as a built-in extension** by adding to `ui/desktop/src/built-in-extensions.json`:
194
+
2.**Bundle as a built-in extension** by adding to either:
195
+
-`ui/desktop/src/built-in-extensions.json` (core built-ins surfaced in extension UI)
196
+
-`ui/desktop/src/components/settings/extensions/bundled-extensions.json` (bundled extension catalog in Settings)
197
+
198
+
Example:
195
199
196
200
```json
197
201
{
@@ -268,6 +272,26 @@ You are an AI assistant called [YourName], created by [YourCompany].
268
272
- Component text and labels
269
273
- Feature visibility
270
274
275
+
5. **Align packaging and updater names** when rebranding:
276
+
- Update static branding metadata in `ui/desktop/package.json` (`productName`, description) and Linux desktop templates (`ui/desktop/forge.deb.desktop`, `ui/desktop/forge.rpm.desktop`)
277
+
278
+
- Set build/release environment variables consistently:
279
+
- `GITHUB_OWNER`and `GITHUB_REPO` for publisher + updater repository lookup
280
+
- `GOOSE_BUNDLE_NAME`for bundle/debug scripts and updater asset naming (defaults to `Goose`)
281
+
282
+
Example:
283
+
284
+
```bash
285
+
export GITHUB_OWNER="your-org"
286
+
export GITHUB_REPO="your-goose-fork"
287
+
export GOOSE_BUNDLE_NAME="InsightStream-goose"
288
+
```
289
+
290
+
6. **Use this branding consistency checklist** before release:
291
+
- Application metadata (`forge.config.ts`, `package.json`, `index.html`) uses your distro name
292
+
- Release artifact names and updater lookup names are consistent
293
+
- Desktop launchers (Linux `.desktop` templates) point to the same executable name produced by packaging
0 commit comments