Open
Description
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:
- The beginning of the Jobs YAML:
jobs:
test:
runs-on: ubuntu-latest
environment: TWITCH-DOWNLOADER
...
- 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
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Backlog 🗒