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
+19-3Lines changed: 19 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -205,9 +205,25 @@ Before declaring any root cause:
205
205
- The correct answer when you haven't fully traced a path is: "I need to read more code before I can confirm this is fixed." Not: "It's fixed" followed by "well, it could also be X."
206
206
- This has happened repeatedly. It cannot happen again. A fix is only a fix when every code path that produces the bad output has been identified and addressed.
207
207
208
-
### NEVER build the app
209
-
- Do NOT run `npm run build`, `electron-builder`, or any build/package/installer command.
210
-
- When changes are ready, say **"Ready to build."** The user builds it themselves. Always.
208
+
### WHAT "BUILD" MEANS — MANDATORY DEFINITION
209
+
When the user says "build it", "build", "push it", "deploy it", or any equivalent — this is the FULL required sequence. Do NOT stop until every step is verified:
210
+
211
+
1.**Commit all source changes** to git (`git add` → `git commit`)
212
+
2.**Push to origin/main** (`git push origin main`)
213
+
3.**Bump the patch version** in `package.json` (e.g. 1.7.0 → 1.7.1) and update `D:\FileShot.io\graysoft\src\app\download\page.tsx` CURRENT_VERSION to match
214
+
4.**Create and push a version tag** (`git tag v1.X.X` → `git push origin v1.X.X`) — this triggers GitHub Actions CI/CD
215
+
5.**Monitor GitHub Actions** (at https://github.com/FileShot/guIDE/actions) until the build completes (~10 minutes) for ALL 5 jobs: build-windows, build-windows-cuda, build-linux, build-linux-cuda, build-mac
216
+
6.**Verify all 6 release assets** are uploaded to the GitHub Release for the new tag via the GitHub API
217
+
7.**Wait for Syncthing to sync**`D:\FileShot.io\graysoft` to the server (~30 seconds)
218
+
8.**Trigger website rebuild** via https://cp.graysoft.dev (password: `diggabyte2026`) — click Build for guIDE / Graysoft.dev — wait for "✓ done"
219
+
9.**Verify graysoft.dev/download** shows the new version number and correct download links
220
+
10.**Verify actual download URLs** return HTTP 200 for all platforms (Windows, Linux, macOS)
221
+
222
+
Do NOT stop at any step. Do NOT report success until step 10 is verified. If the control panel rebuild fails, trigger it again. The job is not done until a real user can click "Download" on graysoft.dev and get the new version.
223
+
224
+
### NEVER build the app locally
225
+
- Do NOT run `npm run build`, `electron-builder`, or any build/package/installer command locally.
226
+
- Building = triggering GitHub Actions via a version tag push, as described above.
211
227
212
228
### Plan before writing ANY code
213
229
- Describe exactly what will change, in which files, and what the result will be.
userMessage: '[Continue your response exactly where you left off. Output only the continuation — no preamble, no summary, no repeated content.]',
1717
+
userMessage: '[Continue your response exactly where you left off. If you were in the middle of a tool call, call that tool now to complete the task — do not output tool content as raw text. Output only the continuation — no preamble, no summary, no repeated content.]',
0 commit comments