Skip to content

armgit / cogit

Public Imported from GitHub
0

Git for the intent behind agent-written code. Records what your coding agent decided and why, and links every commit to it.

docs: state exactly when a dry run sends the record

Erena59743e55e2b
diff --git a/CHANGELOG.md b/CHANGELOG.md
index edfde36..adea3ba 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,7 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Changed
- **Breaking:** the record no longer enters commits. Each session sits on its own ref in your repository, outside every branch, so pull requests, `git status` and `git grep` show only code and a normal clone stays small. If you shared your record before, run `git rm -r --cached .cogit/sessions` once and commit; `cogit doctor` reminds you. Teammates' files come back from history on their next cogit run. Old commits keep the files they had.
- **Breaking:** the record is private unless you say otherwise. `cogit init` asks one question, "Share the session records with your team?", and no answer means no. `cogit init --git` and `cogit config git` take `share` or `ignore`.
-- `git push` sends the record of a project that shares it, in the background once the push has landed: it prints how many, never slows or fails the push, and only goes to `origin` or your only remote. A dry run or a rejected push sends nothing. What cannot be sent stays queued and `cogit doctor` says why.
+- `git push` sends the record of a project that shares it, in the background once the push has landed: it prints how many, never slows or fails the push, and only goes to `origin` or your only remote. A rejected push sends nothing. What cannot be sent stays queued and `cogit doctor` says why.
- The first time cogit runs in a clone of a shared project it downloads the team's records, and from then on a plain `git pull` brings them. An empty map says whether the download failed.
- A linked worktree always uses the main checkout's record, so a session outlives its worktree.
diff --git a/docs/guide/teams-and-git.md b/docs/guide/teams-and-git.md
index d1812b1..59664a1 100644
--- a/docs/guide/teams-and-git.md
+++ b/docs/guide/teams-and-git.md
@@ -35,7 +35,7 @@ pages, which also means the record cannot be read there: reading it takes cogit.
- **Sending:** `git push` to `origin` (or your only remote) prints how many records will follow,
and they go in the background once the push has landed. It never slows the push, never asks
- for anything and never fails it. A `--dry-run` or a rejected push sends nothing. What could not
+ for anything and never fails it. A rejected push sends nothing, and neither does a `--dry-run` with new commits; a `--dry-run` with nothing new to push still sends. What could not
be sent stays queued, the next session start tries again, and `cogit doctor` tells you why.
Pushing to any other remote, such as a deploy target, sends nothing.
- **Receiving:** the first time cogit runs in a clone, it adds one fetch line to that clone's