Repository navigation
Add tests to catch any new HTTP links added to product code #3347
Description
Activity
- added this to the milestone
on Mar 16, 2017 - modified the milestones: ,
on May 15, 2017 microsoft-github-policy-service commented
on Nov 16, 2023 ContributorThis issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented
on Nov 16, 2023 ContributorThis issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented
on Nov 16, 2023 ContributorThis issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented
on Nov 23, 2023 ContributorThis issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.
We should be using HTTPS for all links that are found in product code unless there is a specific reason to use HTTP.
There should be some automation at some point to detect new HTTP links added and verify if a suitable HTTPS counterpart can be used.
Comments from Travis Plunk (@TravisEz13) in PR #3331:
"We could add a meta test suite and use a regex to validate we use https: and not http:
DSC Resources have some meta tests (not for something exactly like this):
https://github.com/PowerShell/DscResource.Tests/blob/dev/Meta.Tests.ps1"