On Mon, 2023-01-16 at 09:34 +0000, c.buhtz@posteo.jp wrote:
Beside the new "main" branch I created the "dev" branch.
Thanks lot for this huge repo change! I could successfully migrate my cloned repo.
@Jürgen: I know you work on some FAQ and maybe README. ... I assume your upcoming docu changes should go into "main" too?
I would only send a PR for dev only since our intention was to keep the dev-doc in sync with the code.
I suggest to merging it into "dev" and then picking the changes from there into "master". I would do that via "git checkout my.file dev". I never used git's cherry pick before. This is one exception of the only-release-commits-in-main because "main" do produce the landing page via its README.md.
Agreed! Changes of the README.md landing page (incl. related) files may always go to "dev" + optionally immediately also to "main" if it is not only related to "dev" code but also for the current release.