Currently, when you call mgit sync it uses the master branch in every repo, unless the repo's branch is defined in mgit.json.
It'd be useful if mgit could also use stable when the main repo is on stable. That would allow us to stop changing mgit.json on ckeditor5#stable which is inconvenient and leads to problems.
Theoretically, we could make mgit sync (and mgit co) use the current branch of the main repo in all cases where the branch is not defined in mgit.json. So, e.g. when ckeditor5 is on t/foo, all repos would be switched to t/foo. But I don't think that this would be that useful because unlike stable, the ticket branches are very rarely defined in all repos. Plus, if you don't need to change mgit.json why would you create t/foo in ckeditor5.
Therefore, I'd like to call this feature e.g. coreBranches and define it in mgit.json like this:
Currently, when you call
mgit sync
it uses themaster
branch in every repo, unless the repo's branch is defined inmgit.json
.It'd be useful if mgit could also use
stable
when the main repo is onstable
. That would allow us to stop changingmgit.json
onckeditor5#stable
which is inconvenient and leads to problems.Theoretically, we could make
mgit sync
(andmgit co
) use the current branch of the main repo in all cases where the branch is not defined inmgit.json
. So, e.g. whenckeditor5
is ont/foo
, all repos would be switched tot/foo
. But I don't think that this would be that useful because unlikestable
, the ticket branches are very rarely defined in all repos. Plus, if you don't need to changemgit.json
why would you createt/foo
inckeditor5
.Therefore, I'd like to call this feature e.g.
coreBranches
and define it inmgit.json
like this: