Open philos3 opened 11 months ago
after exc melos version --all,can we keep the style of flutter yaml version,just like 7.3.28+7328 to 7.3.29+7329
I can understand why you would want to have submodules in your monorepo and connect them to the rest of your packages in there, but to version them from a repository where their code doesn't actually live sounds like a pretty bad pattern since it can't update the versions in their pubspec files or add local changelogs to them. Or maybe I misunderstand your request?
What I want is just the automatic generation module's changelog,and to auto increase the main project version
Is there an existing feature request for this?
Command
melos version --all
Description
melos.yaml
melosExample for repository https://gitlab.melos.pro/mobile/melos [submodule "component/melos1"] for repository https://gitlab.melos.pro/mobile/melos1 [submodule "component/melos2"] for repository https://gitlab.melos.pro/mobile/melos2 [submodule "component/melos3"] for repository https://gitlab.melos.pro/mobile/melos3 [submodule "component/melos4"] for repository https://gitlab.melos.pro/mobile/melos4
here is the chagelog
we can see all the module commit links of chagelog are all start with "https://gitlab.melos.pro/mobile/melos/-/commit/", of course the chagelog links under submodule melos1 、melos2、melos3、melos4 are all wrong,it should be : https://gitlab.melos.pro/mobile/melos1/-/commit/XXXXX https://gitlab.melos.pro/mobile/melos2/-/commit/XXXXX https://gitlab.melos.pro/mobile/melos3/-/commit/XXXXX https://gitlab.melos.pro/mobile/melos4/-/commit/XXXXX
Reasoning
I think it is gread to support submodule repository
Additional context and comments
No response