Merged
Conversation
Member
|
Awesome work! Tested on my end and everything worked great -- just added two todos that we discussed in the PR description |
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.
Recently a few teams have shared that their secrets / PII scanners have been going off because their developers have been putting data into prompts that shouldn't be shared with the Coding Agents / LLMs / Git AI.
All the Git AI features that require raw prompts are experimental and limited in their usage, so we think it makes sense to disable prompt sharing by default and make it easy to turn back on per-repo.
This PR
git-ai configcommand to make it easier to updateconfig.json*for allowed reposgit-ai configcommand in CLI reference