|
|
|
|
|
by anentropic
28 days ago
|
|
What is the intended team workflow with git? I do some work on a PR, Kage generates some new memories - I commit those with the feature? > Branch changes can be summarized with `kage propose --from-diff` and checked with kage pr check. Is this suggested as a pre-commit hook type of activity? Are there actions that should run periodically in CI, or upon merges to base branches? |
|
'kage propose --from-diff' is a supplementary tool that you can use to create a feature summary packet.
'kage pr check' runs validation and graph-freshness, and blocks on hard-stale memory your diff invalidated. You can run 'kage pr check' in your CI as well, that's what Kage is doing it in it's own repo.