feat: add suggested exclude-pattern picker with usage-based ordering
A more user-friendly way to manage exclude patterns could be implemented, potentially with the following features:
-
Dropdown/Checkbox Menu for Common Patterns:
- Allow users to easily select common exclude patterns (e.g.,
*.csv,*.toml,/tests,*.log, etc.). - These patterns could be pre-populated based on common exclusions or usage statistics.
- Allow users to easily select common exclude patterns (e.g.,
-
Repo-Specific Suggestions:
- After the user runs gitingest on a repository, analyze the file types and structures to suggest exclude patterns specific to the repo. For example:
- Identify patterns that would significantly reduce the token count.
- Highlight those patterns in the suggested list.
- After the user runs gitingest on a repository, analyze the file types and structures to suggest exclude patterns specific to the repo. For example:
-
Usage-Based Ordering:
- Order suggested patterns based on global usage statistics (how frequently they are excluded by other users) or the impact they have on the token count for the specific repository being analyzed.
This feature would improve usability by streamlining the process of excluding unnecessary files and directories, helping users optimize their token budgets while interacting with gitingest.
This pre-filling of include/exclude patterns is definitly something I plan on adding in an "advanced settings" menu in the future
The main goal is to provide a good default experience with hidden configuration options All the advanced settings combined together will become a "ingestion preset" that stays broad and high level (like: docs, architecture, implementation)
As we discussed with @filipchristiansen, we could probably sync those settings locally in a .gitingest file format (toml, yml?)
I second (+1) this feature request.
I go from >160k on current "default" experience, to ~3.2k, that's a 98% down. It doesn't help any AI to have .lock files in this experience.
I was thinking of creating a pattern matching and sharing with friends (so the sharing link already has the matching on the query params).
But for that, several of the ideas mentioned here are needed.
This is very useful, please keep up the great work 👍
Hi there! We haven’t seen activity here for 45 days, so I’m marking this issue as stale. If you’d like to keep it open, please leave a comment within 10 days. Thanks!
Hi there! We haven’t heard anything for 10 days, so I’m closing this issue. Feel free to reopen if you’d like to continue the discussion. Thanks!