microsoft / microsoft/VFSForGit

Investigate signing for .NET Core flavor of FastFetch

Open
#623 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

affects: engineering domain: fastfetch
Dominant language
C#
Stars
6.1k
Forks
474
Avg merge
2d 4h
Merged PRs (30d)
8

Description

For both Windows and MacOS self-contained versions.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Begin by locating the .NET Core FastFetch self-contained build process for Windows and macOS, then determine the signing requirements for both flavors. Done means signing is investigated and a concrete implementation path is documented for both platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
release, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.