Open pchakraborty opened 5 months ago
@tclune @amdasilva @mathomp4 Thoughts?
Hmm. Interesting. I'll have to stare at that for a bit to absorb it. Though I suppose the "automatic" grouping is sort of interesting.
Arlindo did look into this prior to proposing the "man pages" you have for HEPO. I don't recall which aspects led him to want to develop a separate tool, but my memory is that he thought gita was a great proof of concept.
gita
(https://github.com/nosarthur/gita) has the concept of repo groups and context. Essentially one can define a repo-group and executegita
commands on this group. This might be helpful when working with several related repositories. https://github.com/nosarthur/gita?tab=readme-ov-file#define-repo-group-and-context.This might be useful for maintaining consistency across a repository hierarchy. For example, if we were make changes in GOCART (a la #288), we might do
GOCART steps
Local
(Local) Step 0: Create hierarchical group
(Local) Step 1: Create branch in GOCART and its upstream repositories
(Local) Step 2: Modify GOCART files and commit
Commit all changes to
feature/<user>/gocart/some-change
in GOCART and its upstream repositories(Local) Step 3: Save current state and update registry
save
ensures that all repositories, that are part ofh-gocart
, are clean, i.e. all sources have been committed to a branch. It then writes a new state file in.mepo
and updates the registry (components.yaml
).(Local) Step 4: Push all changes
Push `feature//gocart/some-change from GOCART and its upstream repositories to remote