INITIALIZED EMPTY GIT REPOSITORY WINDOWS

auto-init in the repo gets us this branch already. Visibility = 'private ' // Creates the 'main' branch with a small 'README.md'

INITIALIZED EMPTY GIT REPOSITORY WINDOWS

Could give me anyone an hint what I do wrong here I have two Gitlab-CI runners on two Windows LTSC VMs. That is easily solved by creating the branch and then re-applying. Initialized empty git repository seems wrong, because there is an git repositories which the runners should operate on (see pipline output below). They're of very limited, and largely dangerous use, when all they do is prevent an error upon creation of a new repo and branch protection of a branch not existing. It seems like adding the new branch and default branch resources was not thought out terribly well. If you do track it, then it will destroy the old one and create a new one, moving the HEAD of that branch. If you don't track your default branch, then it won't create a new one, it'll just destroy the old one. Then there's the problem of changing default branches. So when the repo is neatly archived, all the branches will be gone (or at least all the non-default branches depending on the above implementation). We now have archive_on_destroy but no equivalent for branches. This should be smarter, perhaps always looking up if the branch exists or not and not holding state–just declaring the branch SHOULD exist if it doesn't.Īnd then an end of life problem. If you try to create a branch for what would be the default branch (which makes sense), then it will fail, forcing you to do an import (which is a nightmare). Yes, you need to look up the organization default.Īlso, you have a further impact/problem.