Add prerequisite for public repository to publish

[ShilpaSandbox]

Added prerequisite note about repository visibility for publishing.

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Unable to view the 'Build and Deployment' option under Pages as I had created my repo visibility as Private. 'Build and Deployment' is visible only if if the repo visibility is set to Public.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17 3.16	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17 3.16

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@ShilpaSandbox Thanks for the PR! I have no problem with this information being added, but it belongs in the troubleshooting section that already exists, and it cannot be a heading. Or a note, in this case. The troubleshooting section is already a mess, honestly, so if you just put it in as its own paragraph, I'll accept it for the moment, because the whole thing needs to be rewritten. (Two notes next to each other? Painful.)

[ShilpaSandbox]

Implemented as per suggestion received.

[ShilpaSandbox]

Rewrite this as:

1. Make sure the branch you want to use as your publishing source already exists in your repository. The Repository must be set to Public to view the Build and Deployment.

[ShilpaSandbox]

Remove this line as I have included this in R27.

[ShilpaSandbox]

Updated

[ShilpaSandbox]

Repository needs to be set as Public or else user cannot view the 'Build and Deployment'.

[Antncon5641]

Thank you excellent idea just what it needed