I don’t care which one you use, just don’t change it once it’s established. So many legacy Yocto projects got broken cause open source libraries changed their branch names.
I don’t care which one you use, just don’t change it once it’s established. So many legacy Yocto projects got broken cause open source libraries changed their branch names.
This was one of the arguments when the renaming was first proposed. “Just rename it, it won’t break anything! It’s only racists that want to keep the name!”
Sure, except for all the CI/CD scripts, release scripts, etc that all have “master” there and are now broken.
I know of a company that their entire CI pipeline was broken overnight because some “helpful” person renamed the branch to master but didn’t bother checking out their pipelines…
I know of a company that their entire CI pipeline was broken overnight because some “helpful” person renamed the branch to master but didn’t bother checking out their pipelines
Sounds like the sort of simpleton that would find “master” offensive.
I don’t care which one you use, just don’t change it once it’s established. So many legacy Yocto projects got broken cause open source libraries changed their branch names.
This was one of the arguments when the renaming was first proposed. “Just rename it, it won’t break anything! It’s only racists that want to keep the name!”
Sure, except for all the CI/CD scripts, release scripts, etc that all have “master” there and are now broken.
I know of a company that their entire CI pipeline was broken overnight because some “helpful” person renamed the branch to master but didn’t bother checking out their pipelines…
Sounds like the sort of simpleton that would find “master” offensive.