Repository navigation
Replies: 3 comments 4 replies
|
Actually I think in my case using the code harness for this might be enough. I'll keep thinking about it. |
0 replies
|
I now see that you actually call things like the claude harness from the tool. That makes this easy. Just tell it to make a commit if you see a dirty repo. Tell it to do work on a worktree and make prs. etc. It can use its own naming schema and make its own commit messages and use the github app this way. |
2 replies
|
Thanks for starting discussion! I'm using IWE+Agent+Git a lot and it works great. Usually agents are very capable of using Git properly. I have instructions in CLAUDE.md file to commit every meaningful changes in the knowledge graph and agent usually does it very well. What problem direct integration with git would solve? |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I think it'd be great if we could get the following going optionally:
Alternatives: let the harness do this. But we may not always be using a code harness (might be using copilot or in my case claude from the web).
All reactions