Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare switch from master to main #1275

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

leonard84
Copy link
Member

No description provided.

@codecov
Copy link

codecov bot commented Feb 7, 2021

Codecov Report

Merging #1275 (f523896) into master (ead439b) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            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 data
Powered by Codecov. Last update ead439b...f523896. Read the comment docs.

@Vampire
Copy link
Member

Vampire commented Feb 7, 2021

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.

@leonard84
Copy link
Member Author

The the main 😉 reasons are:

  • the default for github was actually changed to main for 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

@Vampire
Copy link
Member

Vampire commented Feb 7, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants