#Nested projects
1 messages · Page 1 of 1 (latest)
So, my idea is that we have a root project, which will include common actions, and also effectively implement some internal tools in a consistant way e.g. initialising a project from a template repo
Then, the nested projects will be a specific deployment. They will also be dagger projects, where dagger is triggering CI/CD etc
My idea for this is inspired a bit by the push model of cue mentioned in their FOSDEM talk this year https://fosdem.org/2022/schedule/event/cue_pratical_guide/
So, by having a root project, we can push updates to common actions and internal tools in a consistent way, that then bubble up to the nested projects?