Publish Live

[Mikejo5000]

No description provided.

[learn-build-service-prod]

Learn Build status updates of commit 50aa4c8:

💡 Validation status: suggestions

File	Status	Preview URL	Details
docs/reference/Errors-and-Warnings.md	💡Suggestion	View	Details
docs/concepts/Auditing-Packages.md	✅Succeeded	View
docs/nuget-org/media/nuget-org-permissions.png	✅Succeeded	View
docs/nuget-org/media/nuget-org-register-2fa.png	✅Succeeded	n/a (file deleted or renamed)
docs/nuget-org/media/nuget-org-register.png	✅Succeeded	View
docs/nuget-org/media/unmanaged-aad-tenant.png	✅Succeeded	View
docs/reference/errors-and-warnings/NU1508.md	✅Succeeded	View
docs/reference/errors-and-warnings/NU1901-NU1904.md	✅Succeeded	View
docs/reference/media/registered-certs.png	✅Succeeded	View
docs/reference/nuget-config-file.md	✅Succeeded	View
docs/release-notes/NuGet-6.12.md	✅Succeeded	View
docs/TOC.md	✅Succeeded	View

docs/reference/Errors-and-Warnings.md

• Line 28, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Mikejo5000]

@zivkan Andy, are your changes OK to publish live?

[zivkan]

are your changes OK to publish live

yes. Frankly I don't understand the purpose of having separate live and main branches. If we wanted to stage changes until a particular time, we could have used a feature branch 🤷

I feel like the different live & main branches unnecessarily delays useful docs updates.