Create a Pull Request (git pull) by adding one or more reviewers option?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reviewing the relationship between Commands.Pull, PullOptions, and the requested pull-request and reviewer workflow described in the issue. Check whether the repository exposes an entry point for that workflow; done should be a clear supported-or-not answer, with any required scope identified.
Written by the indexing model from the issue text.
Description
I am using .NET 5.0 Using libgit2sharp 0.26.0, I've written code to clone , create a new branch, change some files, commit and push branch to bitbucket.
Now I need to create a pull-request and add a reviewer to it. However, my Google searches don't turn up any relevant info.
Does libgit2sharp support creating PRs by adding reviewer? Any help
using (var repo = new Repository(LocalRepoUrl))
{
Signature Signature = new Signature(Username, Email,
new DateTimeOffset(DateTime.Now.Year,
DateTime.Now.Month, DateTime.Now.Day,
DateTime.Now.Hour,
DateTime.Now.Minute, DateTime.Now.Second,
TimeSpan.FromHours(2)));
FetchOptions fetchOptions = new FetchOptions();
fetchOptions.CredentialsProvider = (_url, _user, _cred) => new UsernamePasswordCredentials
{
Username = Username,
Password = Password
};
MergeOptions mergeOptions = new MergeOptions();
mergeOptions.IgnoreWhitespaceChange = true;
mergeOptions.FailOnConflict = true;
mergeOptions.CommitOnSuccess = true;
mergeOptions.FastForwardStrategy = FastForwardStrategy.Default;
PullOptions pullOptions = new PullOptions();
pullOptions.FetchOptions = fetchOptions;
pullOptions.MergeOptions = mergeOptions;
// how to add reviewer
var mergeResult = Commands.Pull(repo, Signature, pullOptions); // no pull request generated
Please correct me if I am wrong and suggest me with the correct code.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
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.
More from libgit2/libgit2sharp
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
libgit2/libgit2sharp#2193 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
libgit2/libgit2sharp#2192 · 1 comment ·
-
Website is down Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
libgit2/libgit2sharp#2191 · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
libgit2/libgit2sharp#2189 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
libgit2/libgit2sharp#2187 · 2 comments ·
All issues in libgit2/libgit2sharp
Similar issues
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
kind/bug kind/regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
unoplatform/uno.toolkit.ui#1646 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nightscout/nocturne#1379 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
elastic/esql-dotnet#47 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100