Skip to content

/plugin marketplace add should prefer shallow sparse checkout from pluginRoot #2341

@JanKrivanek

Description

@JanKrivanek

Describe the feature or problem you'd like to solve

Support repos containing stuff beyond just plugins

Proposed solution

Searching through github.com - there is nontrivial amount of repos publishing plugins alongside of the non-plugin code/infra/etc: https://github.com/search?q=path%3A**%2Fmarketplace.json+plugins&type=code

Not to force publisher to separate those into separate repo nor to force user to checkout unrelated stuff to their machines - we can use the pluginRoot metadata to indicate and fetch only relevant plugins.

Example prompts or workflows

dotnet/skills repo has plugins in .\plugins folder. Everything else is not intended for plugins consumers, but for the plugin authors and maintainers

Observing the pluginRoot would help keeping all the maintainer relevant stuff in same repo, while not pushing it to customers machines

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions