microsoft / microsoft/winget-cli

Clone and configure a GitHub project

Open
#4,435 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Command-Configure Issue-Feature
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Description of the new feature / enhancement

I'd like to simplify the process of cloning and configuring a GitHub project.

The trivial syntax would look something like this:
winget configure https://github.com/microsoft/winget-cli

Gaps:

  • WinGet would need to ensure Git is on the system (it might need to be updated).
  • WinGet would need to have a default behavior with respect to where to clone the repository.
  • The user should be able to specify where the clone should happen on their filesystem.
  • If more than one configuration is available, the user should be able to specify.

This would also greatly simplify the process for users on a new system getting their personal configuration set up just the way they like. It also means the user would need to remember the raw GitHub URL for their configuration.

I'm still working on my stuff, and it probably is broken, but I'd like to be able to run the following command on any machine I use so all my favorite stuff is installed and configured:

winget configure https://github.com/denelon/setup

Suggested by @acangialosi

Proposed technical implementation details

No response

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

Start with the requested winget configure command and the listed gaps: Git availability, clone location, filesystem destination, and selecting among multiple configurations. Review the existing configuration and source-control command behavior before deciding how the GitHub URL and configuration selection should work. Done means the feature's behavior and scope are defined for the example command and its edge cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, git, github
Domain
cli, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.