89bc69cf3b
## Summary
- New **Support CodeNomad** help page (10 languages): what sponsorship
pays for, the funding policy (a contribution, not a purchase; never
required to download, use or update) and one button per funding channel
naming who receives the money.
- **Download page** ends with a short *Support development* section with
the same buttons; the help **header** gains a *Sponsor* link; the former
support page is retitled **Bug reports and source builds** (ids
unchanged) so the two are not confused.
- **App**: *Support CodeNomad* in Settings → Info (secondary button
between Updates and Diagnostics), in the Help menu after *CodeNomad
Help* (Electron and Tauri, English help-page fallback) and as a palette
command without a default shortcut. All open the localized help page.
- **Repository**: `.github/FUNDING.yml` lists the maintainer's GitHub
Sponsors profile and the Support page (the Sponsor button needs
*Settings → General → Features → Sponsorships*).
Channels live in `docs/help/funding.json` and render through a
`{{funding}}` directive allowed only on the download and sponsor pages,
so adding a channel needs no retranslation. Entries are validated (exact
keys, unique ids, `https://github.com/sponsors/<login>` only) and
escaped; a page using `{{funding}}` with no channel fails the build. CSP
unchanged.
Agreed with the co-maintainer before publishing.
## Validation
- `npm run test:help`: 31/31 (27 pages × 10 locales, funding validation
and placement).
- `node scripts/test-help-browser.mjs`: 47/47 (header overflow at 390 px
in en/he/ne/ja/zh-Hans, button geometry).
- `npm run typecheck`; unit tests help-url, hotkey-bindings,
menu-labels; browser tests help-command, server-info, view-menu-electron
(22/22); `cargo test` for the Tauri crate (291/291, including the
English sponsor fallback).
- Independent review: zero findings.
7.7 KiB
bug report र source build
bug report, current release र contribution का लागि repository प्रयोग गर्नुहोस्। issue report अघिको सुरक्षित recovery समस्या समाधान गाइड मा छ।
bug report गर्नुहोस्
- सेटिङहरू → जानकारी → निदान (Diagnostics) खोल्नुहोस्।
- GitHub issue form खोल्न बग रिपोर्ट गर्नुहोस् चयन गर्नुहोस्।
- prefilled version/client जानकारी समीक्षा गर्नुहोस्। न्यूनतम reproduction, अपेक्षित व्यवहार र वास्तविक नतिजा थपेर GitHub बाट बुझाउनुहोस्।
कार्यले CodeNomad र OpenCode version (स्थापित भन्दा फरक हुँदा चलिरहेको OpenCode सेवासमेत), तपाईंको operating system, client प्रकार (web browser मा browser को user agent सहित) र server को operating system पूर्वभर्छ। listener address, workspace path, credential वा conversation text भर्दैन। form खोल्नु issue बुझाउनु होइन।
थप निदान चाहिए क्लिपबोर्डमा प्रतिलिपि गर्नुहोस् वा .txt डाउनलोड गर्नुहोस् ले छुट्टै report बनाउँछ। त्यस विस्तृत report मा local path र network address हुन सक्छन्: attach अघि review/redact गर्नुहोस्। automatic diagnostic report ले authentication secret हटाए पनि screenshot वा log अंशमा secret हुन सक्छन्।
GitHub form मा incompatible field भए CodeNomad ले उही report जानकारीसहित plain issue खोल्छ। form पढ्दाको अस्थायी failure ले खोल्न रोक्दैन। सधैं issue सूची हातैले प्रयोग गर्न सकिन्छ।
समुदाय र release
| स्रोत | प्रयोग |
|---|---|
| CodeNomad repository | source, project गतिविधि र documentation। |
| Issues | reproducible bug वा feature request खोल्नुअघि विद्यमान report खोज्नुहोस्। |
| Pull requests | प्रस्तावित परिवर्तन समीक्षा वा contribution समन्वय। |
| डाउनलोड पृष्ठ | तपाईंको प्लेटफर्मका लागि नवीनतम stable desktop build। |
| नवीनतम release | stable download artifact। |
| सबै release | published preview र release note। |
| Neural Nomads | project संगठन। |
| MIT license | license सर्त। |
CodeNomad नियन्त्रणभन्दा native OpenCode configuration का समस्यामा OpenCode दस्तावेज र upstream release हेर्नुहोस्।
source बाट build
.node-version मा pinned Node.js 24.20.0, npm, Git र compatible OpenCode CLI प्रयोग गर्नुहोस्। development checkout बाट आदेश चलाउनुहोस्:
git clone --branch dev https://github.com/NeuralNomadsAI/CodeNomad.git
cd CodeNomad
npm ci --workspaces --include=optional
npm run dev
npm run dev ले Electron development host सुरु गर्छ। Tauri मा पहिले Rust toolchain समेत platform build prerequisites स्थापना गरी चलाउनुहोस्:
npm run dev:tauri
development परिवर्तनले development host प्रभावित गर्छन्, स्वतन्त्र चलिरहेको OpenCode daemon को installed version होइन। native packaging लाई उचित target tool चाहिन्छ; target OS मै build प्राथमिकता दिनुहोस्।
build र validation
| repository root बाट command | उद्देश्य |
|---|---|
npm run build |
Electron application resource build। |
npm run build:tauri |
native prerequisite सहित Tauri application build। |
npm run build:ui |
browser UI build। |
npm run build --workspace @neuralnomads/codenomad |
standalone server र bundled asset build। |
npm run build:linux --workspace @neuralnomads/codenomad-electron-app |
Electron Debian release package। |
npm exec --workspace @codenomad/tauri-app -- tauri build --bundles appimage |
Linux Tauri AppImage package। |
npm run typecheck |
root का configured TypeScript workspace जाँच। |
npm run test:help |
सबै public-help locale र link validation। |
npm run build:help |
standalone public help dist/help मा build। |
help build लाई running CodeNomad वा OpenCode service चाहिँदैन। packaging विवरणका लागि BUILD.md, scoped validation र PR convention का लागि CONTRIBUTING.md हेर्नुहोस्; target package मा वास्तवमै भएका script प्रयोग गर्नुहोस्।
package नक्सा र योगदान
| Package | जिम्मेवारी |
|---|---|
packages/server |
workspace/API/Git नियन्त्रण, OpenCode जडान, auth, event र speech। |
packages/ui |
SolidJS workspace, नियन्त्रण, localization र browser help entry point। |
packages/electron-app |
Electron window, native integration र packaging। |
packages/tauri-app |
Tauri window, platform integration र packaging। |
packages/remote-tunnel |
backend-side OpenTunnel transport runtime। |
- overlap हुने काम लागू गर्नुअघि सम्बन्धित issue मा scope छलफल गर्नुहोस्।
devबाट branch बनाई परिवर्तन केन्द्रित राख्नुहोस्।- प्रभावित क्षेत्रका check चलाउनुहोस्, व्यवहारसँग user help update गर्नुहोस् र PR
devमा लक्षित गर्नुहोस्।
public help स्रोत docs/help/<locale>/ मा छन्। अनुवादमा हरेक English heading को explicit ID, level र order जोगाउनुहोस्; translated heading ले deep link बिगार्नु हुँदैन। help maintenance contract ले कडा completeness check र static publishing pipeline बताउँछ।