Add proper markdown to 'main'

[a2br]

What:

I have changed "main" to main.

Why:

Below the 'main' section, in the 'master' section, master is used, not "master".

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[janiceilene]

@a2br Thanks so much for opening a PR! I'll get this triaged for review 💖

[github-actions]

This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit.

[a2br]

Still waiting for review.

[janiceilene]

@a2br Thanks for your patience! Our small team is working our way through reviewing all of the amazing contributions ✨

[felicitymay]

Hi @a2br 👋🏻

Thanks for your patience. Your change to the data/glossaries/external.yml file looks good 😄

I'm less sure about the changes to the translated files. On the whole, we don't accept changes to those files but maybe formatting changes are safe. I'll check with our localization team and let you know how we can get your changes merged.

[a2br]

Ok! I can still revert the commits on the translation files.

[felicitymay]

Ok! I can still revert the commits on the translation files.

I hadn't noticed that they were in separate commits. That would be great. Many thanks.

[a2br]

Done! ✅

[felicitymay]

💖 Many thanks for reverting those commits. This looks ready to merge now 🚢

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours.

[felicitymay]

@a2br 👋🏻 Bonjour 😄

Since I merged your pull request, I've been getting email notifications about Actions workflow failures in your fork. This puzzled me. I looked into it.

I think you enabled Actions in the settings for your fork. The failing workflow synchronizes the docs repository with our internal systems. It uses a token that your fork does not have access to. To avoid using up your Actions minutes, you should turn off actions in your fork of the docs repo (Disabling or limiting GitHub Actions for a repository).

I raised this with the docs engineering team and they will update the synchronization workflow so that it does not run on forks. The work is not scheduled yet, so it would be good to turn off actions for this repository.

[a2br]

Actions are now disabled in my fork ☑️

[felicitymay]

💐 Thank you. I hope that this hasn't cause problems for you in your fork.

We usually create a feature branch from main with the changes we want to merge into the main branch of the docs repository. This would also help avoid problems like this in any future changes you propose to the docs repository.

[a2br]

Yes, that's what I usually do. Since the change here was very small, I thought i'd just delete my fork and re-fork if needed in the future. Thanks for the reminder though.

[felicitymay]

That makes sense. Some of the contributors to this repository are just starting out with git and GitHub, so I thought I should mention it. It's great to hear that you already knew.

Have a great weekend 👋🏻