microsoft / microsoft/VFSForGit
Revisit how FastFetch is distributed to engineering systems teams
Open
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
Now that FastFetch has more than one consumer, we should revisit and formalize how partners are supposed to consume updates. We don't want to return the old state of installing FastFetch with VFSForGit.
The first thing that comes to mind is to have it as another item (.zip/.tar) in each GitHub release.
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
The issue names no files or tests. Start by reviewing how FastFetch is currently installed with VFSForGit and how GitHub releases are packaged. Done should define and implement a formal partner-consumption path, including whether FastFetch is distributed as a separate .zip or .tar release item.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100