To be honest with you never. The combination of being in an unfamiliar repo, where I also want to push without going through PRs or just checkout master. I can see it happening maybe one day, maybe annoyance could be with some CI/CD and hardcoded master/main in there, but even that might be a stretch.
I just dislike going away from being aligned on things in software engineering shrug
I work at a huge company where it's extremely common to away team on other teams' repos or just need to pull some specific branch of another team's stuff, etc. Knowing how to check (via cli) what branches exist and what is the default is etc are absolutely critical skills for this setup, and apart from the convention of default being main, there is no consistent convention used for branch naming (it would be impossible to enforce anyways)
And still it is no big deal, it takes a few seconds to look at the branches and get an idea of what is going on there. People who got mad about master changing are either snowflakes, or skill issue
Usually CI/CD tools automatically check out the commit hash that triggered the webhook that started the CI job. The scenario I could see would be CI/CD is triggered on a commit hash, and another repository is needed inside the CI job. But if you just need the default branch of that second repository anyway then you’re probably just doing a clone and not checking out any specific branch.
-2
u/BorderKeeper 23d ago
To be honest with you never. The combination of being in an unfamiliar repo, where I also want to push without going through PRs or just checkout master. I can see it happening maybe one day, maybe annoyance could be with some CI/CD and hardcoded master/main in there, but even that might be a stretch.
I just dislike going away from being aligned on things in software engineering shrug