microsoft / microsoft/VFSForGit
Don't allow --no-verify when upgrading on platforms that support verification
Open
Nobody has claimed this yet.
affects: polish
affects: security
platform: windows
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
See full discussion here: https://github.com/microsoft/VFSForGit/pull/1510#discussion_r321471050https://github.com/microsoft/VFSForGit/pull/1510#discussion_r321471050
Consider removing the --no-verify option on platforms that support verification (or only allow it in developer builds).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named; start with the linked PR #1510 discussion and locate the upgrade command handling --no-verify. Done means the option's behavior is defined for verification-capable platforms, including whether developer builds are an exception, with the resulting behavior verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100