Answer prose round 1: 0 🔴, 5 🟡 (0 misread); say up front that only project-config reads the config yet
CI / tests (pull_request) Successful in 2m45s
CI / tests (pull_request) Successful in 2m45s
This commit was merged in pull request #516.
This commit is contained in:
+1
-1
@@ -2,7 +2,7 @@
|
||||
|
||||
## Unreleased
|
||||
|
||||
- Each project now has a config, `~/.claude-projects/<key>/config.toml`, that names its checkout and the path of every file the loop keeps for it. `project-config` prints those paths, and fails naming each setting a config leaves out. README → Install → "Set up a project" shows how to write one. The other tools don't read the config yet.
|
||||
- A project can now have a config, `~/.claude-projects/<key>/config.toml`, that names its checkout and the path of every file the loop keeps for it. `project-config` prints those paths, and fails naming each setting a config leaves out. README → Install → "Set up a project" shows how to write one. The other tools don't read the config yet, so nothing breaks without one; a later release will need one for every project.
|
||||
- larv-review takes an item as a floor item only where its tagline opens with `Reach the comprehension floor:`. A tagline that quotes the floor elsewhere, such as in a decision title, no longer makes its chunk due a scoring run. Reword each open floor item's tagline in every project's `todo.md` to open with the phrase.
|
||||
|
||||
## 0.9.0
|
||||
|
||||
@@ -77,9 +77,9 @@ To get loop-claude's questions and stops as Mattermost DMs from a bot, write the
|
||||
|
||||
### Set up a project
|
||||
|
||||
Each project the loop runs in has a config, `~/.claude-projects/<key>/config.toml`, where `<key>` is the project's name. The folder is a git repo of its own, so the config has a history and a client's files never enter this repo. A project is a whole git checkout, never a subfolder of one.
|
||||
Each project the loop runs in has a folder, `~/.claude-projects/<key>/`, where `<key>` is the project's name, and a config in it, `config.toml`. The folder is a git repo of its own, so the config has a history and a client's files never enter this repo. A project is a whole git checkout, never a subfolder of one.
|
||||
|
||||
The config names the project's main checkout and the path of every file the loop keeps for it. No setting has a default: `project-config` fails and names each setting a config leaves out. A path is `checkout:<path>` inside the checkout, `folder:<path>` inside the config's folder, or one that starts with `/` or `~/`. A project of your own keeps every file in its checkout:
|
||||
The config names the project's main checkout and the path of every file the loop keeps for it. No setting has a default: `project-config` fails and names each setting a config leaves out. A path is `checkout:<path>` inside the checkout, `folder:<path>` inside the config's folder, or one that starts with `/` or `~/`. Today only `project-config` reads the config: every other tool still reads each file at the place this example gives it. A project of your own keeps every file but the principles in its checkout:
|
||||
|
||||
```toml
|
||||
checkout = "~/code/log"
|
||||
@@ -94,7 +94,7 @@ goals-and-audience = "checkout:README.md"
|
||||
principles = "~/.claude/principles"
|
||||
```
|
||||
|
||||
For a client's project, use one sandbox VM per client, so that one client's code, transcripts and credentials never share a machine with another's. Keep what the client's repo should not hold in the config's folder: write those paths as `folder:<path>`, as `project-config --help` shows.
|
||||
For a client's project, use one sandbox VM per client, so that one client's code, transcripts and credentials never share a machine with another's. What the client's repo should not hold will live in the config's folder, at paths written as `folder:<path>`, as `project-config --help` shows. Until the other tools read the config, write the client's config like the example above.
|
||||
|
||||
```sh
|
||||
mkdir -p ~/.claude-projects/acme && cd ~/.claude-projects/acme
|
||||
@@ -104,7 +104,7 @@ git add config.toml && git commit -m "Add the config"
|
||||
cd ~/code/acme-billing && ~/.claude/bin/project-config
|
||||
```
|
||||
|
||||
The last line prints each setting's path once the config is complete. Today only `project-config` reads the config: every other tool still reads each file at the place the example above gives it.
|
||||
The last line prints each setting's path once the config is complete.
|
||||
|
||||
## Update
|
||||
|
||||
|
||||
Reference in New Issue
Block a user