Skip to content

Feature spec: evaluate Gallery and Extension Management APIs #51

Description

@CompN3rd

Summary

Evaluate whether Azure DevOps Gallery / Extension Management APIs have any useful role in ADOExt.

Product rationale

Gallery and Extension Management are low fit for ADOExt. Developers rarely manage Azure DevOps organization extensions from VS Code, and the browser/admin UI is usually the right tool. This issue exists to capture the decision and prevent accidental scope creep unless a compelling user request appears.

Possible UX, if ever implemented

Prefer command palette shortcuts or browser links over a full view.

Potential read-only data:

  • Installed Azure DevOps extensions for the organization
  • Extension status/version
  • Open extension management in browser

Integration with existing core features

No strong integration with Work Items, Pull Requests, Planning, or Pipelines is currently identified.

MVP scope

No MVP recommended at this time.

Non-goals

  • Installing/uninstalling Azure DevOps extensions from VS Code.
  • Browsing marketplace extensions.
  • Managing organization extension permissions.

Acceptance criteria for revisiting

Only revisit this if there is a concrete user request that ties extension management to a developer workflow in ADOExt.

If revisited:

  • Keep it read-only by default.
  • Avoid adding a permanent sidebar view.
  • Prefer browser links for admin actions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions