libgit2 / libgit2/libgit2sharp
LibGit2Sharp.Tests case where it pulls recent remote change and then checks it out?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
I am having issues with getting REALLY RECENT new object commits when I do a pull/checkout of a branch. I looked through the Tests and didn’t see anywhere that was obviously doing this sort of test. Is there one?
Reproduction steps
Commit a brand new object using GitHub website.
Do a Commands.Pull/Commands.Checkout of the branch containing the object
Expected behavior
See new object
Actual behavior
Object is missing. Of note, I found that for some reason, if I get EVERY branch in the repo and then checkout the branch I actually need, I’ll end up with the new object most of the time (but not every time).
Version of LibGit2Sharp (release number or SHA1)
0.25.2
Operating system(s) tested; .NET runtime tested
Windows 7, Windows 10, .NET 4.7.1
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
Start in LibGit2Sharp.Tests by locating coverage for Commands.Pull and Commands.Checkout. Reproduce the sequence with a newly committed object from the GitHub website, then verify whether the checked-out branch exposes that object; done means the behavior is understood and covered by a reliable test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100