3 ms·
Even existing projects??? No, that's not going to break tons of stuff and tooling built and running on production around "master" /s
by axegon_ 6y ago
Even existing projects??? No, that's not going to break tons of stuff and tooling built and running on production around "master" /s
- Jonnax 6y agoHas someone said that's what they're doing? Have you seen more information about this change? Because the link here is just saying "that's a good idea and we're working on it" in response to someone asking about changing the default branch name. Like default sounds like new project creation time.
- axegon_ 6y agoThat's what I'm asking. I mean there are probably tons and tons of custom built tools, ci/cd's around the current default "master" branch. It would be awesome to wake up and see a ton of alarms and all builds and deployments failing, wouldn't it.
- Jonnax 6y agoIn that case. It's very likely to be done to existing projects. Creating a different branch requires commiting to the repo, at least from what I understand. And and branch name is just a text field.