[PR #184] [MERGED] feat: load every environment from --env-file to workflow #1378

New issue

Closed

opened 2026-03-01 21:50:56 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 21:50:56 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/nektos/act/pull/184
Author: @jonyhy96
Created: 4/3/2020
Status: ✅ Merged
Merged: 4/17/2020
Merged by: @cplee

Base: master ← Head: feat_dot_env

📝 Commits (6)

b49a19c feat: load every environment from --env-file to workflow
de9d319 Merge branch 'master' into feat_dot_env
d3689ce Merge branch 'master' into feat_dot_env
bca8b09 fix: pass dotenv's environments through by context
82d8d3f updates to support --secret-file
ebfcb3e Merge pull request #1 from nektos/feat_dot_env

📊 Changes

10 files changed (+47 additions, -30 deletions)

View changed files

📝 .gitignore (+1 -0)
📝 cmd/input.go (+6 -0)
📝 cmd/root.go (+25 -10)
📝 pkg/runner/run_context.go (+1 -1)
📝 pkg/runner/runner.go (+1 -0)
📝 pkg/runner/runner_test.go (+3 -13)
📝 pkg/runner/testdata/secrets/.actrc (+1 -3)
📝 pkg/runner/testdata/secrets/.env (+2 -3)
➕ pkg/runner/testdata/secrets/.secrets (+3 -0)
📝 pkg/runner/testdata/secrets/push.yml (+4 -0)

📄 Description

As mentioned in #124 and #179, users are confused about the flag --env-file behavior.

So i think it is better to make it easier for user to use the .env file to set up some environments they want to use in the further workflow.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/nektos/act/pull/184 **Author:** [@jonyhy96](https://github.com/jonyhy96) **Created:** 4/3/2020 **Status:** ✅ Merged **Merged:** 4/17/2020 **Merged by:** [@cplee](https://github.com/cplee) **Base:** `master` ← **Head:** `feat_dot_env` --- ### 📝 Commits (6) - [`b49a19c`](https://github.com/nektos/act/commit/b49a19c96bc7a2b1da5c0449919c1314665b2510) feat: load every environment from --env-file to workflow - [`de9d319`](https://github.com/nektos/act/commit/de9d31901c0c136bef5fb72218e69af36a8e2eb6) Merge branch 'master' into feat_dot_env - [`d3689ce`](https://github.com/nektos/act/commit/d3689cefe8f006f0546ca0b2a0c01bf789a49b38) Merge branch 'master' into feat_dot_env - [`bca8b09`](https://github.com/nektos/act/commit/bca8b09e52cde04b9d4a8f1ba6dc3f6118081c4a) fix: pass dotenv's environments through by context - [`82d8d3f`](https://github.com/nektos/act/commit/82d8d3f2f547a5a7c594975ff71245bcad19ec17) updates to support --secret-file - [`ebfcb3e`](https://github.com/nektos/act/commit/ebfcb3e6a2edf523641c27577243e51ea17af475) Merge pull request #1 from nektos/feat_dot_env ### 📊 Changes **10 files changed** (+47 additions, -30 deletions) <details> <summary>View changed files</summary> 📝 `.gitignore` (+1 -0) 📝 `cmd/input.go` (+6 -0) 📝 `cmd/root.go` (+25 -10) 📝 `pkg/runner/run_context.go` (+1 -1) 📝 `pkg/runner/runner.go` (+1 -0) 📝 `pkg/runner/runner_test.go` (+3 -13) 📝 `pkg/runner/testdata/secrets/.actrc` (+1 -3) 📝 `pkg/runner/testdata/secrets/.env` (+2 -3) ➕ `pkg/runner/testdata/secrets/.secrets` (+3 -0) 📝 `pkg/runner/testdata/secrets/push.yml` (+4 -0) </details> ### 📄 Description As mentioned in #124 and #179, users are confused about the flag `--env-file` behavior. So i think it is better to make it easier for user to use the .env file to set up some environments they want to use in the further workflow. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-03-01 21:50:56 +03:00

closed this issue
added the
pull-request
label

kerem referenced this issue

2026-03-01 21:53:13 +03:00

[PR #1378] [MERGED] build(deps): bump github.com/imdario/mergo from 0.3.12 to 0.3.13 #1915

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1378

No description provided.

Rows
Columns