git-ai
git-ai copied to clipboard
acunniffe
Track the AI-generated code in your repos
Add configurable file ignore patterns to `git-ai stats` command, allowing users to exclude specific files (like lockfiles) from authorship statistics. - [x] Update command - [x] Add+update tests - [x]...
Git blame with specified hunks can be significantly faster in the best case (all lines found in recent commits and traversal can stop early). We should explore only collecting blame...
Rewriting authorship for especially large rebases does not need to block git command. We can collect the shas we need, dispatch them to a bg git ai thread, and let...
Checkpoints don't need to actually do diffs, load blame and move around attributions. We could make them save all the current contents file blobs and relevant repo state, and wait...
I'm not 100% sure how this occurred in our repo, but I've got cases whereby we have attestations in a `git-ai` note for a commit, but no prompts, which causes...
## Summary This PR enables git-ai debug logging when the `GIT_TRACE` environment variable is set. This allows developers debugging Git operations to automatically see git-ai debug output without needing to...
In codespaces (on git-ai 1.0.22), the attribution is flaky, especially for new files. I attach logs and chat export in case this helps. [logs.txt](https://github.com/user-attachments/files/23755577/scratch5.txt) [chat.json](https://github.com/user-attachments/files/23755578/scratch9.json) and the stats are :...
Since the copilot agent chat session data is stored in the workspace storage, we need to build special support for remote VSC and codespaces In codespaces, these chat JSON logs...