Add sentry open <url> to resolve any Sentry URL

未关闭
#1,889 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
api, cli

调研方向

Read the linked CLI parity inventory and task 2.8, then inspect existing CLI commands that accept URL positionals and the MCP get_sentry_resource implementation. Identify the resources and command entry points the issue expects sentry open <url> to cover, then add unit tests and tick the corresponding parity rows; confirm the permission and exposure requirement against #1880.

由索引模型根据 Issue 内容生成。

描述

CLI enhancement

Part of #1357 and #1382 (CLI parity with the MCP). Plan: cli-first-mcp task 2.8 (parity table, tasks).

Under the CLI-first plan the MCP runs CLI commands instead of its own catalog tools, so every catalog tool needs a command before the catalog can go. New commands call the API through @sentry/api operations. They don't wait for the client move (#1875).

Gap

The MCP's get_sentry_resource takes any Sentry URL and returns the resource. Most CLI commands accept URL positionals, but there is no single entry point.

Scope

sentry open <url> resolves the URL to its resource (issue, event, trace, replay, release, dashboard, monitor, …) and returns it, or names the command that shows it.

Done when

  • The commands land with unit tests, and their parity-table rows in the design are ticked.
  • Each command has a permission class and exposure (#1880), if that has landed.

via @BYK.

--

View Session in Sentry

主要语言
TypeScript
星标
961
派生
179
平均合并
15 小时 33 分钟
30 天内合并 PR
476

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

getsentry/toolkit 的其他 Issue

查看 getsentry/toolkit 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。