Update rugged to 0.25.1.1
What does this MR do?
It updates rugged
to 0.25.1.1. It's a continuation of !8538 (closed).
Are there points in the code the reviewer needs to double check?
libgit2
redefined sorting options, I updated the code, the discussion starts here - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8538#note_22461988
Why was this MR needed?
New version of rugged
has a few bug fixes that we need.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary [ ] Documentation created/updated[ ] API support added- Tests
[ ] Added for this feature/bug-
All builds are passing
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/17325
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/14972
Closes #14765 (closed)
Merge request reports
Activity
mentioned in merge request !8538 (closed)
added 4190 commits
-
6e04c5ca...f8275ec9 - 4190 commits from branch
master
-
6e04c5ca...f8275ec9 - 4190 commits from branch
This should (hopefully) also fix #14765 (closed).
@thomasjachmann Thanks for spotting this. Yes, it looks like this should also solve that problem. I added it to the description.
@adamniedzielski That was easy to spot, since that bug has been preventing me from fully moving a client's team from GitHub to GitLab for several months now. Can't wait to complete that step. :)
assigned to @rspeicher
@rspeicher can you review?
No data yet, but I hope this will also fix #26179 (moved).
- Resolved by Robert Speicher
mentioned in issue #26179 (moved)
mentioned in issue #17019 (moved)
mentioned in issue #30973 (closed)
mentioned in commit 0ddc402e
mentioned in merge request !10936 (merged)