Would you accept PRs for this extension?

[CombeeMike]

Question

Would you be willing to accept PRs from me if I'd find the time to contribute to your extension?

I'm currently writing quite a few feature requests here b/c I think that I'll be using your extension a lot after migrating some private & work projects from multi to monorepo setups.

The work projects are co-developed by ~ 10 devs and I'd like to introduce this extension to them as well after migrating to the monorepo which is why I'm looking very actively for ways to optimize the current featureset for our use cases.

Obviously I'd only start PRs after first asking for your "go" and having some "agreed upon" basic concept to not put time into some feature which you don't want to see in your extension.

Another option would be to create a fork e.g. if my feature requests don't align with your product vision for the extension.

I'm asking purely hypothetical b/c I don't know for sure whether or not I'd actually find the time to contribute...

[dimateos]

Let me ping you https://github.com/sfccdevops/explorer-exclude-vscode-extension/issues/64 which details my 2 issues with the extension.

I feel those would be very relevant for shared local workspace settings in team + groups globs would help with large filter lists.

I guess if you are motivated another feature I would add for long globs is a name mapping like:

• "**/{pycache,.pytest_cache}" -> _pycache, so the UI panel renders friendlier stuff
  • or e.g. for subprojects A B C -> backend
  • could also drop all ** etc

I also feel like it would be best to make PR to the original repo, but given the license you can always have a public fork for the time being. Just saying because maybe you already implemented some of what I asked for XD

Regards