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.

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

Supply secrets with a .env file #58

Closed
Djiit opened this issue Apr 17, 2019 · 3 comments
Closed

Supply secrets with a .env file #58

Djiit opened this issue Apr 17, 2019 · 3 comments

Comments

@Djiit
Copy link

Djiit commented Apr 17, 2019

It would be great to be able to provide some sort of .env file to avoid prompting user each time you run a workflow.

@Haegin
Copy link

Haegin commented Apr 25, 2019

If the secret vars are in the current environment it seems that act uses them automatically. I moved from using .env files to using direnv a while back as that loads environment vars into the environment automatically when you cd into a directory and unloads them when you leave. Because the env vars are in the environment tools then don't need to support a .env file, they just need to support reading environment vars which every language I've used can do natively.

@maxheld83
Copy link
Contributor

I've documented this in a PR: #66

@cplee
Copy link
Contributor

cplee commented Feb 25, 2020

Support is now available to provide default vals via .actrc

@cplee cplee closed this as completed Feb 25, 2020
makrsmark pushed a commit to makrsmark/act that referenced this issue Aug 3, 2023
Partially resolve go-gitea/gitea#24789.

`act_runner`  needs to be improved to parse `gitea_default_actions_url` after this PR merged (https://gitea.com/gitea/act_runner/pulls/200)

Co-authored-by: Lunny Xiao <[email protected]>
Reviewed-on: https://gitea.com/gitea/act/pulls/58
Reviewed-by: Lunny Xiao <[email protected]>
Reviewed-by: Jason Song <[email protected]>
Co-authored-by: Zettat123 <[email protected]>
Co-committed-by: Zettat123 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants