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

Unrecognized Github Actions Secret Context

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

还没有人认领这个 Issue。

评估

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

调研方向

首先,使用提供的 jobs YAML、名为 TWITCH-DOWNLOADER 的环境,以及工作流中引用的两个环境 secret 重现该警告。跟踪 GitHub Actions Extension 如何验证 secret 和环境上下文;当环境 secret 在没有 missing-or-undefined 警告的情况下被识别时,即表示完成。

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

描述

bug

Describe the bug

  • I have a GitHub Actions workflow, VSCode recommended me the Extension.
  • And i use the Environment Feature for GitHub Action Secrets.
  • This is not recognized by the Extension,
    • even that the Environment Secrets works when i let the Action run.
    • Even more frustrating:
      • there seems to be no option to ignore or comment out that warning that the secret isn't valid
      • we need an option to ignore that if the Extension fails to read the environment context

To Reproduce
Steps to reproduce the behavior:

  1. The beginning of the Jobs YAML:

jobs:
test:
runs-on: ubuntu-latest
environment: TWITCH-DOWNLOADER
...

  1. The Step that Uses the Secrets:
  • name: Schreibe Secrets in .env-Datei
    run: |
    echo "TWITCH_CLIENT_ID=${{ secrets.TWITCH_CLIENT_ID }}" >> .env
    echo "TWITCH_CLIENT_SECRET=${{ secrets.TWITCH_CLIENT_SECRET }}" >> .env

The Repo itself private, but i guess the error is easy to reproducible with

  • create a repo
  • creating a environment with that name (in https://github.com/(user)/(repo)/settings/secrets/actions)
  • creating 2 Secrets named like that in that environment
  • creating a github action yaml file with just that step above
  • Save
  • The Yaml loaded into VSCode with the GitHub Actions Extension running
    X the Secrets will be recognized as missing or not defined X

Expected behavior
To recognize the Environment and the Secrets in there

主要语言
TypeScript
星标
661
派生
214
PR 合并指标
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

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

github/vscode-github-actions 的其他 Issue

查看 github/vscode-github-actions 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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