Open ahpook opened 3 months ago
@ahpook
I like this idea.
A thought and a couple questions:
Thought:
~/.githubospo
(not married to the name) file that has all the contents from each repositories .env-sample
or README environment variables (some are not in the samples currently) in there. Like asked above, if exists, it will be used and then fall back to repo directory .env
file.Questions:
.env
file. I ask this because when the actions run they will be told where the environment variables are located, usually in repo secrets (e.g, ${{ secrets.GH_APP_ID }}
)~/.githubospo
or repo_dir/.env
)? Or do we parse from both. I prefer the former, easier to manage. Otherwise you have to set expectation on presidence re: overwrites (i.e, GH_APP_ID
is in ~/.githubospo
and also in repo_dir/.env
, which has presidence?)I'm also looking at possibly doing a composite GitHub action for env handling https://docs.github.com/en/actions/creating-actions/creating-a-composite-action
https://docs.github.com/en/actions/creating-actions/creating-a-composite-action
I'd definitely be in support of this!
Currently, the various ospo actions are completely independent. But users who adopt several of them end up restating a lot of configuration for them which would ideally be centralized. As concrete examples, setting:
would be better served by a common configuration file that all of the actions know to look for.