Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Full-Context awareness in a Git repository or Folder #360

Closed
Hexdigest123 opened this issue Jun 12, 2024 · 6 comments · Fixed by #627
Closed

Full-Context awareness in a Git repository or Folder #360

Hexdigest123 opened this issue Jun 12, 2024 · 6 comments · Fixed by #627
Labels
enhancement New feature or request

Comments

@Hexdigest123
Copy link

Hi, I wanted to ask if there's a plan for implementing full-context awareness in Git repositories or in general, projects opened in Neovim. Currently, I only find the option to choose between a single buffer or multiple buffers. If this is not currently possible, is it possible to customize the context for Copilot?
@jellydn jellydn added the enhancement New feature or request label Jun 15, 2024
@jondkinney
Copy link

I would also love this! 🙌

@jellydn
Copy link
Contributor

jellydn commented Jul 19, 2024

FYI - You might want to look to this discussion https://discord.com/channels/1200633211236122665/1209115196702859294/1261373682542968842

TLDR: not yet.

@tmillr
Copy link

tmillr commented Jul 27, 2024 •
edited
Loading

I dont event get my whole project/dir (or rather, not even "all open buffers" as documented) as context when using @buffers...only 2 or 3 of my open buffers max. Is this the norm, or am I doing something wrong? How much context do you guys get? It wouldn't be a big deal if context was limited, but 2-3 random buffers is nothing.

@deathbeam deathbeam mentioned this issue Sep 12, 2024
Closed
@deathbeam
Copy link
Collaborator

#495

For now this was added, that should help AI to at least figure out structure of the project

@deathbeam
Copy link
Collaborator

I dont event get my whole project/dir (or rather, not even "all open buffers" as documented) as context when using @buffers...only 2 or 3 of my open buffers max. Is this the norm, or am I doing something wrong? How much context do you guys get? It wouldn't be a big deal if context was limited, but 2-3 random buffers is nothing.

Also very late reply, but we use github embeddings queries to determine if something should be included in context or not. and this is based on your prompt query so sometimes it can just ditch less relevant files. Also it depends on maximum token limit, but for example claude can handle a lot of data.

deathbeam added a commit to deathbeam/CopilotChat.nvim that referenced this issue Nov 28, 2024
@deathbeam
feat(context): add full file content support for files
bb16705 
The files context provider now supports two modes:
- 'list' (default) - includes only filenames in the workspace
- 'full' - includes both filenames and their content

This change provides more flexibility when needing full context from workspace
files. The implementation also adds proper filetype detection and filtering
for files to ensure only text files are included.

Closes CopilotC-Nvim#360
@deathbeam deathbeam mentioned this issue Nov 28, 2024
Merged
deathbeam added a commit to deathbeam/CopilotChat.nvim that referenced this issue Nov 28, 2024
@deathbeam
feat(context): add full file content support for files
ee31698 
The files context provider now supports two modes:
- 'list' (default) - includes only filenames in the workspace
- 'full' - includes both filenames and their content

This change provides more flexibility when needing full context from workspace
files. The implementation also adds proper filetype detection and filtering
for files to ensure only text files are included.

Closes CopilotC-Nvim#360

Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
deathbeam added a commit to deathbeam/CopilotChat.nvim that referenced this issue Nov 28, 2024
@deathbeam
feat(context): add full file content support for files
abbafb7 
The files context provider now supports two modes:
- 'list' (default) - includes only filenames in the workspace
- 'full' - includes both filenames and their content

This change provides more flexibility when needing full context from workspace
files. The implementation also adds proper filetype detection and filtering
for files to ensure only text files are included.

Closes CopilotC-Nvim#360

Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
deathbeam added a commit that referenced this issue Nov 28, 2024
@deathbeam
feat(context): add full file content support for files
ed7234c 
The files context provider now supports two modes:
- 'list' (default) - includes only filenames in the workspace
- 'full' - includes both filenames and their content

This change provides more flexibility when needing full context from workspace
files. The implementation also adds proper filetype detection and filtering
for files to ensure only text files are included.

Closes #360

Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
@deathbeam deathbeam mentioned this issue Nov 28, 2024
Closed
@deathbeam
Copy link
Collaborator

Ok this is now mostly implemented with files:full context, feel free to try :) There is no caching atm so it only works well for small to mid sized repositories, but its usable. For rest see #628

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(context): add full file content support for files deathbeam/CopilotChat.nvim
5 participants
@jondkinney @jellydn @deathbeam @tmillr @Hexdigest123