Switch master to main

[andrewtavis]

Switching over the default branch in the examples to main to match current standards. I also wrote a note to explain the switch from master, which I tried to not make too outspoken while suggesting that main should be the default of choice. By all means feel free to make the note more blunt, and hope this helps :)

What was wrong/why is this fix needed? (quick summary only)
The examples are still using "master", which is no longer the default.

MDN URL of main page changed
https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Deployment

Issue number (if there is an associated issue)
N/A

Anything else that could help us review it
For the note, I used this article as a reference for October 2020.

[rachelandrew]

I wonder if there is a good link to share in that note as to why this change is suggested?

[andrewtavis]

I was looking for one, as I also thought it'd help. There really wasn't an announcement made about all this. The only reference I could find was to a tweet by Nat Friedman in June 2020, which is when people knew that it would happen (that is the source on all the news websites around that time). There really is no substance though.

There's also the renaming repo for GitHub that makes it clear that the change is suggested, but then does not provide a justification. That repo is the one that's referenced across GitHub channels as where people should go to learn more about the change. A link with a justification that they use in that readme comes from Software Freedom Conservancy and Git, which starts with the following, but doesn't go further:

Both Conservancy and the Git project are aware that the initial branch name, ‘master’, is offensive to some people and we empathize with those hurt by the use of that term.

I think that the above is as strong a comment from an organization related to this change as we're going to find, and it's also referenced on BitBucket and GitLab. The comment could potentially be changed to reference "version control services" and then that link would fit:

Until 2020 the default branch on Git and Git based version control services was master, which for various social reasons was switched to main. You should be aware that this older default branch may appear in projects you encounter, but we'd suggest using "main" for your own projects.

[github-actions]

Preview URLs

• https://pr4480.content.dev.mdn.mozit.cloud/en-US/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Deployment

Flaws

URL: /en-US/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Deployment
Title: Deploying our app
on GitHub
Flaw count: 1

• broken_links:
  • Link points to the page it's already on

External URLs

URL: /en-US/docs/Learn/Tools_and_testing/Understanding_client-side_tools/Deployment
Title: Deploying our app
on GitHub

• https://near-misses.netlify.com (1 time) (Note! This may be a new URL 👀)

(this comment was updated 2021-05-20 12:42:20.103160)

[peterbe]

At this point, it's not a controversial "social/civil" issue because the new default is main on GitHub.
I approve but with nits.

[Ryuno-Ki]

I actually did some research last year for freeCodeCamp/chapter#434

[wbamberg]

@andrewtavis , Peter had some comments on this which were marked resolved, but I don't see the changes in the diff. Did you mean to accept the suggestions? I'm happy to merge this if we can resolve them.

[andrewtavis]

@wbamberg, my apologies. I had been worried that something else was needed on my end for this. I was a bit confused on how I couldn't directly approve the changes in the review of them, so I just resolved them. I guess I didn't see how to do that properly.

With this being said, I accept the changes fully and you can merge :)

[peterbe]

Hi @andrewtavis You ignored my suggestions. You marked them as resolved.
You need to either press the "Commit suggestion" (first you might need to "Unresolve conversation") or do it manually in your code editor.

[andrewtavis]

@peterbe, thanks for the directions on that! Didn't realize the difference between resolving and committing the changes. I thought that we were waiting for Chris' review on all this. Appreciate your explanation!

[chrisdavidmills]

I don't think I need to review this as well, so removing myself from the list to avoid any more holdups.

[wbamberg]

@peterbe, thanks for the directions on that! Didn't realize the difference between resolving and committing the changes. I thought that we were waiting for Chris' review on all this. Appreciate your explanation!

No worries, @andrewtavis . You would not be the first person to be confused by this bit of GitHub's UI :).