mirror of
https://github.com/nektos/act.git
synced 2026-04-26 17:35:49 +03:00
[GH-ISSUE #58] Supply secrets with a .env file #31
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#31
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Djiit on GitHub (Apr 17, 2019).
Original GitHub issue: https://github.com/nektos/act/issues/58
It would be great to be able to provide some sort of
.envfile to avoid prompting user each time you run a workflow.@Haegin commented on GitHub (Apr 25, 2019):
If the secret vars are in the current environment it seems that
actuses them automatically. I moved from using.envfiles to usingdirenva while back as that loads environment vars into the environment automatically when youcdinto a directory and unloads them when you leave. Because the env vars are in the environment tools then don't need to support a.envfile, they just need to support reading environment vars which every language I've used can do natively.@maxheld83 commented on GitHub (May 20, 2019):
I've documented this in a PR: https://github.com/nektos/act/pull/66
@cplee commented on GitHub (Feb 25, 2020):
Support is now available to provide default vals via .actrc