dotnet / dotnet/install-scripts
Provide guidance on how users should be doing "freshness" checks on install scripts
Open
- Dominant language
- PowerShell
- Stars
- 213
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
We would like to be able to write a test that validates if our CDN copy matches repo copy. I know that GitHub Actions does this as well. This would help ensure that users only pickup up copies that we have high confidence in and only feel compelled to update their script at (no more than) a monthly cadence. Basing that all off of `main` seems like not the best model.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.