-
Notifications
You must be signed in to change notification settings - Fork 495
Add a general HTTPS everywhere doc #3498
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
Conversation
|
Learn Build status updates of commit 09340b5: 💡 Validation status: suggestions
docs/consume-packages/nuget-https-everywhere.md
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces comprehensive documentation explaining NuGet's HTTPS Everywhere enforcement policy. The new article explains why HTTP package sources are now blocked and provides clear guidance on resolution.
- Adds conceptual documentation on NuGet HTTPS Everywhere enforcement
- Explains error NU1302, opt-out options, and HTTPS enforcement rollout timeline
- Integrates new content into the documentation table of contents
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/consume-packages/nuget-https-everywhere.md | New conceptual article explaining HTTPS Everywhere policy, errors, and configuration options |
| docs/TOC.md | Adds table of contents entry for the new HTTPS Everywhere article under Configure NuGet section |
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
|
Learn Build status updates of commit a98afb2: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit 90ed2a2: ✅ Validation status: passed
For more details, please refer to the build report. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
nkolev92
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for creating this doc.
| ### [Package Manager Console (PowerShell)](consume-packages/install-use-packages-powershell.md) | ||
| ## Configure NuGet | ||
| ### [Visual Studio options](consume-packages/nuget-visual-studio-options.md) | ||
| ### [NuGet HTTPS Everywhere](consume-packages/nuget-https-everywhere.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if this concept needs its own heading.
I wonder if it should be contained within some sources write-up.
I couldn't find a source write-up, so I'm not gonna ask you to write a new doc for this. I'm curious what others think.
We can always leave it as is and then do some more docs later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had a similar question in the beginning; however, I did not find perfect spot where I could put this doc in. I will look again. If there are any suggestions, please let me know.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree this seems like it should not be a top-level section, but I think we can edit the Index easily enough later.
donnie-msft
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! Have a few tweaks and edit suggestions.
| ### [Package Manager Console (PowerShell)](consume-packages/install-use-packages-powershell.md) | ||
| ## Configure NuGet | ||
| ### [Visual Studio options](consume-packages/nuget-visual-studio-options.md) | ||
| ### [NuGet HTTPS Everywhere](consume-packages/nuget-https-everywhere.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree this seems like it should not be a top-level section, but I think we can edit the Index easily enough later.
|
Learn Build status updates of commit cfa9e46:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/consume-packages/nuget-https-everywhere.md | View | Details | |
| docs/TOC.md | ✅Succeeded | View |
docs/consume-packages/nuget-https-everywhere.md
- Line 21, Column 17: [Warning: file-not-found - See documentation]
Invalid file link: 'release-notes/NuGet-6.12.md'.
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.
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
|
Learn Build status updates of commit b857da5: ✅ Validation status: passed
For more details, please refer to the build report. |
donnie-msft
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Looks very close!
|
Learn Build status updates of commit ab8710f: ✅ Validation status: passed
For more details, please refer to the build report. |
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
Adds the documentation page users are redirected to when visiting
https://aka.ms/nuget-https-everywhere.The link appears in HTTP-related errors across Visual Studio, .NET SDK, and NuGet CLI.
This page explains HTTPS enforcement, how to resolve or opt out of HTTP source errors, and links to related docs like