Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Move the Dependabot alert sweep from the nonexistent PROJECT_TOKEN to the GitHub App token

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
github-actions
领域
ci-cd, devops

调研方向

Start with .github/workflows/dependabot-alerts.yml around line 103 and the related references in AGENTS.md; confirm the GitHub App from #2544 is available before changing the token flow. Check the workflow's fallback and run verify:action-pins, then validate that a test alert is both filed and placed on board #28 at Todo/High, while missing App secrets still produce the triage hand-off.

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

描述

blocked chore v2

Problem

.github/workflows/dependabot-alerts.yml (line 103) passes secrets.PROJECT_TOKEN to the sweep, so that it can place each filed issue on board #28 at Todo / High. That secret has never existed, so every run degrades to filing a labeled, milestoned issue that waits for manual /issue-triage.

Change

Once the GitHub App exists (#2544), switch the workflow to it:

  • Add an actions/create-github-app-token step, SHA-pinned (verify:action-pins, #2484), that mints an installation token from the App id and private key secrets.
  • Pass that token to the sweep in place of PROJECT_TOKEN, and delete the PROJECT_TOKEN path and its references in the workflow comments and AGENTS.md.
  • Keep the degrade-to-triage fallback, so a run with the secret missing (a fork, for example) still files issues and stays green.
  • Consider moving the alert read to the App as well (Dependabot alerts: read) so the sweep runs under one identity. The workflow's vulnerability-alerts: read already works, so this is optional.

Acceptance

  • A scheduled or dispatched run files a test alert's issue and boards it at Todo / High on #28
  • With the App secrets absent, the run still files the issue and logs the triage hand-off
  • verify:action-pins passes, and no PROJECT_TOKEN reference remains

Blocked on

#2544 (the GitHub App). Part of tracker #2543.

主要语言
TypeScript
星标
11.1k
派生
1.5k
平均合并
4 小时 4 分钟
30 天内合并 PR
170

环境准备

从这里开始

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

modelcontextprotocol/inspector 的其他 Issue

查看 modelcontextprotocol/inspector 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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