Commands.Run(string repoUrl, params string[] commands) missing

Open
#1,997 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, git
Domain
api

Research direction

Start by locating the Commands.Run entry points and any existing command-execution tests. Compare the requested overload with the examples for local paths and repository URLs, then add coverage showing that multiple commands and each listed URL form are supported.

Written by the indexing model from the issue text.

Description

A great option to be added is: Commands.Run(string repoUrl, params string[] commands) method.

Examples:

Commands.Run(@"D:\repo", $"ls-remote {fromRepo} refs/heads/master");
Commands.Run(@"D:\repo", $"fetch --force --progress {fromRepo} master");
Commands.Run(@"file:///D:/repo", $"checkout master");
Commands.Run(@"file://localhost/repo", $"reset --hard FETCH_HEAD");
Commands.Run(@"git://localhost/repo", $"reflog expire --expire-unreachable=now --all", $"gc --prune=now");
Commands.Run(@"http://localhost/repo", $"update-server-info");
Dominant language
C#
Stars
3.5k
Forks
925
PR merge metrics
No merged PRs in 30d

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.

More from libgit2/libgit2sharp

All issues in libgit2/libgit2sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.