StrictKnownMarketplaces - support for Git UrlPattern like github.com/<organization> to allow remote branches and not just main branch

Resolved 💬 2 comments Opened Apr 3, 2026 by Prasanna1985-jav Closed May 23, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

We are looking to restrict the StrictKnownMarketplaces to only our organization's internal marketplace and may be few official ones..
If we have a remote branch part of the marketplace repo, there is no easy way to use that for testing. No option to allow any branches part of a repo to be added as a marketplace. Only main branch can be added.
Host Pattern doesnt support github.com/organization-name format
{
"source": "github",
"repo": "organization-name/claude-plugin-marketplace"
},
{
"source": "git",
"url": "git@github.com:organization-name/claude-plugin-marketplace.git"
}

If I add a new plugin and want to share that remote branch for internal use for a small group of users, it is not possible at this time with an existing StrictKnownMarketplaces available for that repo.

Any workarounds available? I couldn't find any documentation.

Proposed Solution

Can the git source be enhanced to support urlPattern so that any remote branch part of that repo can be added along with this??
I can tag a branch name but that has to be static and everyone should create a branch with same branch name.
Looking to support dynamic branch names part of that repo.
{
"source": "git",
"urlPattern": "git@github.com:organization-name/claude-plugin-marketplace.git"
}
{
"source": "git",
"url": "git@github.com:organization-name/claude-plugin-marketplace.git",
"allowAllBranches": "true"
}

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

I have a internal organization marketplace repo configured with StrictKnownMarketplaces in managed-settings.
By default, it is restricted to main branch.
I am adding a new plugin not ready to share with larger organization
Create a remote branch and share it with others.
When others try to add the remote branch part of the marketplace repo, it is not allowed as
"Enterprise policy would block it since remote branch is not allowed"

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗