Prepare switch from master to main
Codecov Report
Merging #1275 (f523896) into master (ead439b) will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #1275 +/- ##
=========================================
Coverage 76.74% 76.74%
Complexity 3779 3779
=========================================
Files 405 405
Lines 11495 11495
Branches 1402 1402
=========================================
Hits 8822 8822
Misses 2193 2193
Partials 480 480
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update ead439b...f523896. Read the comment docs.
Do we really needed to follow this non-sense movement of exaggerated anti-racism?
Imho we should stick to what Git uses as default which still is master.
The the main 😉 reasons are:
- the default for github was actually changed to
mainfor any new repositories - git itself is preparing to change it 1 2
- it is actually shorter to type
- and junit5 is also already using it
Well first and last are no valid reasons imho as mentioned earlier.
Third is not really an argument as you either have a tool where you can select it, or have tab completion usually.
As mentioned, for me the only valid reason would be the second, but only after it really made it into a release which is still not the case as your link 1 proves.
I still have hopes that someone stops this non-sense that now also forbids to watch various Disney movies.