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

Support nested .vscodeignore files #896

Open
AArnott opened this issue Sep 5, 2023 · 1 comment
Open

Support nested .vscodeignore files #896

AArnott opened this issue Sep 5, 2023 · 1 comment
Assignees
@benibenj
Labels
feature-request Request for new features or functionality info-needed Issue requires more information from poster

Comments

@AArnott
Copy link
Member

AArnott commented Sep 5, 2023

The vsce package command seems to only notice a .vscodeignore file at the root of the package. This is cumbersome and can lead to merge conflicts in a large extension and team.

Can vsce be enhanced to support distributing such files around the repo, the way .gitignore can?
@joaomoreno joaomoreno added the feature-request Request for new features or functionality label Sep 21, 2023
@joaomoreno joaomoreno added this to the April 2024 milestone Mar 26, 2024
@joaomoreno joaomoreno changed the title Distributed .vscodeignore files Support multiple .vscodeignore files Mar 27, 2024
@joaomoreno joaomoreno changed the title Support multiple .vscodeignore files Support nested .vscodeignore files Mar 27, 2024
@kieferrm kieferrm mentioned this issue Apr 8, 2024
Closed
53 tasks
@benibenj
Copy link
Contributor

benibenj commented Apr 9, 2024 •
edited

@AArnott would #867 possibly be a better solution in your case? It's an allow list instead of an ignore list. If not, could you go a bit more into detail why nested .vscodeignore files would be more helpful for you?

@benibenj benibenj added the info-needed Issue requires more information from poster label Apr 10, 2024
@benibenj benibenj removed this from the April 2024 milestone Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@benibenj benibenj

Labels
feature-request Request for new features or functionality info-needed Issue requires more information from poster
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@AArnott @joaomoreno @benibenj