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.

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

Add option to only exclude in "Repository Files", but not in "Repository Structure" #181

Open
awakia opened this issue Nov 24, 2024 · 1 comment
Labels
enhancement New feature or request needs discussion Issues needing discussion and a decision to be made before action can be taken

Comments

@awakia
Copy link

awakia commented Nov 24, 2024

Hi @yamadashy , really nice work. I love this tool.

By the way, why don't you add option only exclude in "Repository Files"?
Currently, --ignore option both exclude in "Repository Structure" and "Repository Files".

For example, my target repository has this kind of file:

📈 Top 5 Files by Character Count and Token Count:
──────────────────────────────────────────────────────
1.  apps/frontend/src/app/fixtures/transcripts1.json (1145024 chars, 377136 tokens)
2.  apps/frontend/public/locales/en/common.json (192476 chars, 82151 tokens)
3.  apps/admin/public/assets/CompanySign.svg (185918 chars, 132207 tokens)
...

In this case, I don't want to store file content but want to include in repository structure.

I think --exclude option is one good name for this purpose.

@yamadashy
Copy link
Owner

yamadashy commented Nov 24, 2024

@awakia
Thanks for the great suggestion! I agree that keeping files in the structure while excluding their content would be really useful.

I considered using --exclude, but it might cause confusion with the existing --ignore option.

Instead, here's my initial draft:

{
  "ignore": {
    "useGitignore": true,
    "useDefaultPatterns": true,
    "customPatterns": ["node_modules/**"],
    "ignoreContentCustomPatterns": ["**/*.svg", "**/*.json"]  // New option
  }
}

CLI would be:

--ignore-content "**/*.svg,**/*.json"

This preserves existing behavior while adding content-only exclusion. Still thinking through the naming though - what do you think about this approach?

@yamadashy yamadashy added enhancement New feature or request needs discussion Issues needing discussion and a decision to be made before action can be taken labels Nov 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs discussion Issues needing discussion and a decision to be made before action can be taken
Projects
None yet
Development

No branches or pull requests

2 participants