Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[CI] - Put all CI steps on GITHUB_OUTPUT (remove GITHUB_ENV) #53

Open
dev-dull opened this issue Feb 8, 2025 · 0 comments
Open

[CI] - Put all CI steps on GITHUB_OUTPUT (remove GITHUB_ENV) #53

dev-dull opened this issue Feb 8, 2025 · 0 comments
Labels
good first issue

Comments

@dev-dull
Copy link
Owner

dev-dull commented Feb 8, 2025

CI uses a mix of GITHUB_ENV and GITHUB_OUTPUT. The use of GITHUB_ENV is leftover from initial development. It should be possible to consolidate on GITHUB_OUTPUT.

PyTerraBackTyl/.github/workflows/docker-build.yaml

Line 25 in 3f2e781

# TODO: going to both ENV and OUTPUTS is probably redundant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dev-dull