github / github/vscode-github-actions

Make sure envs created during steps are also recognized

Open
#147 2 comments 3 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
660
Forks
213
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**
image
As shown below, the value of GITHUB_ENV created during execution is not recognized by extention.
However, since this method is officially recommended by GitHub https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable I think the created env should also be able to recognize it.

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Additional context**
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing a workflow that writes an environment variable through GITHUB_ENV during execution, then trace where the extension recognizes workflow environments. Done means variables created by steps using the documented GITHUB_ENV method are recognized by the extension.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ci-cd, devtools
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.