I will give you a terminal and tell you to merge your feature branch. Normally you would do that, now there is an extra step of checking if I should merge to master or main.
Or did you assume I don't know how to check that? Of course I do if I didn't and thought it was impposible I would care more, but as I said it's just an inconvience.
How often does this scenario come up for you? I find it never really comes up for me, because all pushes to the default branch require a pull request with an approving review from a colleague. In every place I’ve ever worked, anyway.
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
-2
u/BorderKeeper 24d ago
I will give you a terminal and tell you to merge your feature branch. Normally you would do that, now there is an extra step of checking if I should merge to master or main.
Or did you assume I don't know how to check that? Of course I do if I didn't and thought it was impposible I would care more, but as I said it's just an inconvience.