Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clone and configure a GitHub project #4435

Open
4 tasks
denelon opened this issue May 1, 2024 · 3 comments
Open
4 tasks

Clone and configure a GitHub project #4435

denelon opened this issue May 1, 2024 · 3 comments
Labels
Command-Configure Issue related to WinGet Configuration Issue-Feature This is a feature request for the Windows Package Manager client.

Comments

@denelon
Copy link
Contributor

denelon commented May 1, 2024

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

@denelon denelon added Issue-Feature This is a feature request for the Windows Package Manager client. Command-Configure Issue related to WinGet Configuration labels May 1, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label May 1, 2024
@denelon denelon removed the Needs-Triage Issue need to be triaged label May 1, 2024
Copy link

github-actions bot commented May 1, 2024

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@Trenly
Copy link
Contributor

Trenly commented May 1, 2024

WinGet would need to have a default behavior with respect to where to clone the repository.

I think this could be just like git, where the present working directory is used

@acangialosi
Copy link
Member

acangialosi commented May 1, 2024

A possible extension of this concept could be using the well-known DSC configuration on the local machine with a parameter like "--use-default-configuration". It would enable an iterative workflow like the one below.

git checkout release-v1.0.11451
winget configure --use-default-configuration
##build, test, code in older code base##
git checkout main
winget configure --use-default-configuration
##resume work on main branch##

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Command-Configure Issue related to WinGet Configuration Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

No branches or pull requests

3 participants