Your Apps in Action

Use this form to visualize JSON Schema for Azure DevOps Extensions.


{{repoTitle.MainEntity}}

categories Array of strings representing the categories your extension belongs to.

# Values Actions
{{$index+1}}.
targets The products and services supported by your integration or extension.

# id version Actions
{{$index+1}}.
scopes Authorization scopes required by your extension.

# Values Actions
{{$index+1}}.
demands Capabilities required by your extension.

# Values Actions
{{$index+1}}.
.icons
_

tags Array of string tags to help users find your extension.

# Values Actions
{{$index+1}}.
galleryFlags Array of string tags to classify your extension within the Visual Studio Marketplace

# Values Actions
{{$index+1}}.
.licensing
_

.galleryproperties
_

screenshots Screenshots are more valuable when featured in your content, and should be used there to help make a quality market details page for your extension. Use screenshots for less important images not featured in your content.

# path Actions
{{$index+1}}.
.content - Dictionary of content files that describe your extension to users.
_

.links - Dictionary of links that help users learn more about your extension, get support, and move.
_

.repository - The source code repository for the extension
_

badges Approved Badge Sites: https://docs.microsoft.com/en-us/azure/devops/extend/develop/manifest.#approvedbadges

# href uri description Actions
{{$index+1}}.
.branding
_

files The files section is where you reference any files you wish to include in your extension. You can add both folders and individual files.

# path addressable packagePath Actions
{{$index+1}}.
contributions An array of contributions to the system.

# Actions
{{$index+1}}.
contributionTypes An array of contribution types defined by the extension

# Actions
{{$index+1}}.
{{repoTitle.MainEntity}}

{{repoTitle.MainEntity}}

{{repoTitle.MainEntity}}

{{repoTitle.MainEntity}}


{{message}}