Sand box #226
Open
Sand box #226
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Every conversion is pegged to a new folder in your hard coded file path (default: /Users/test/gitrepo/projects)
We create new branches after 'X' amount of files change, which can be configured in the code base.
Github Sync: You can turn on the toggle on the setting page of the app, in order to push your local branches remotely to GH with LLM generated commit messages.
Your data is stored in the hidden folder .kibitz/api/project.json, which contains essential information for retrieval and rollback, such as commit hash IDs, branch names, file changes, timestamps, commit messages, and the base branch each repo is created from.
Kibitz lives in frontend whereas ws-mcp lives in a dockerized container which talks to frontend via TCP