Ref DB: Expose method to allocate a new reflog - #7041
Open
mburtka wants to merge 1 commit into
Open
Conversation
Contributor
|
The name should follow the existing naming schema (such as |
scutuatua-crypto
approved these changes
Apr 3, 2026
|
bump |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi there,
I was trying to interop with C# and create a custom refdb backend. I was unable to allocate a new
git_reflogto implementread_reflog. Thereflog_allocthat already existed in the fs implementation of a ref db has nothing restricting it to file system usage, so I moved to collocate with otherreflogimplementations and exposed it as part of the API (as a semi-private).