Is .gitignore respected?

[nodesocket]

Does this respect .gitignore to prevent sending secrets, passwords, api keys to 3rd parties? Thanks.

[TerminalFi]

By default..no it does not. Is that a feature in the VSCode implementation?

You can likely achieve this by removing the text from the selector setting.

"selector": "source | text | embedding"

If this is a feature that the VSCode version supports. Let me know, I'd like to support it.

[nodesocket]

@TerminalFi that's a great question. Some very trivial testing I did in a project with a .gitignore in VSCode with CoPilot enabled seems to indicate changes in files which are in the .gitignore are being suggested by CoPilot. So, that's very concerning.

I opened a discussion on the official GitHub CoPilot community if you want to follow along and maybe upvote? https://github.com/orgs/community/discussions/51183

[TerminalFi]

Sure, also I think that is a reasonable request and perhaps we can support it via our plug-in as an interim. Will look into it.

[TerminalFi]

@jfcherng @timfjord Thoughts on this feature being supported?

2023-05-04_20-43-29.mp4

[TerminalFi]

@nodesocket Would this type of implementation meet your expectations?

Essentially LSP-copilot is still enabled in this file. However it respects the .gitignore and updates the status bar. So the Language server still knows you are working in a supported file type but since it is in the .gitignore it will NOT send requests to Copilot

[TerminalFi]

I fixed the flashing on the statusbar

[jfcherng]

Related to #106

[neverbot]

I think the Copilot people are working in a .copilotignore specification. Using VS Studio - Insiders it gives the file a specific icon, and Copilot Chat seems to think the file is already working.

I posted it in the github community discussions.

[TerminalFi]

Awesome, so perhaps I can close the MR and wait

[TerminalFi]

#169

[TerminalFi]

https://github.com/TerminalFi/LSP-copilot/releases/tag/v0.2.14