huncode/goon-game
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Настроить обязательный push в origin

Browse Source
This commit is contained in:
huncode
2026-08-18 00:50:44 +03:00
parent 499d3fe802
commit 5aa879623e
3 changed files with 30 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+7 -3
View File
@@ -14,16 +14,20 @@ bd ready --exclude-type epic
Claim the selected bead before changing code and close it only after its acceptance criteria and relevant checks pass. Create follow-up beads for newly discovered work and connect real blockers with `bd dep add`.
The current Beads database is local-only embedded Dolt. No Git or Dolt remote is configured, so do not claim that changes were pushed. At the end of a session:
The Git remote is `origin` at `ssh://git@git.pryanik.synology.me:2222/huncode/goon-game.git`; `master` tracks `origin/master`. The Beads database uses embedded Dolt. A Dolt remote entry exists locally, but publishing the separate Dolt history requires explicit owner authorization; normal `git push` publishes the versioned `.beads/issues.jsonl` snapshot, not the embedded database.
At the end of a session:
1. run the relevant quality gates;
2. update or close the active bead;
3. run `bd dep cycles` after dependency changes;
4. export a readable snapshot with `bd export --output .beads/issues.jsonl`;
5. commit local source and tracking changes when appropriate;
6. report explicitly that synchronization remains local until a remote is configured.
5. commit source and tracking changes;
6. run `git pull --rebase` and `git push`;
7. verify `git status --short --branch` shows the branch tracking `origin/master` without local changes.
Do not edit `.beads/issues.jsonl` manually. The source of truth is `.beads/embeddeddolt`.
Do not run `bd dolt push` unless the owner explicitly authorizes publishing that separate tracking history.
## Build and tests