GitRepository: Support additional upstream extensions #1469
Conversation
Upstream git is actively working on extensions that should be treated as known, even if they are currently experimental, as they do not break these targets. `objectFormat` and `compatObjectFormat` are used to support SHA256 hashes: https://git-scm.com/docs/hash-function-transition `refStorage` is used to support the new `reftable` binary storage backend: https://git-scm.com/docs/reftable These extensions offer performance and security benefits, and we should expect to see more users trying them out before they become the default in git 3.0. See https://about.gitlab.com/blog/what-s-new-in-git-2-51-0/#planning-towards-git-30 for details about what may be coming in git 3.0.
|
With SHA256 enabled, couldn't references now contain SHA256 instead of SHA1, which would result in an exception thrown when we read these? |
I thought the target just reads them as strings? |
|
Could you add |
|
For the |
|
For But libgit2/libgit2#6191 explains that not supporting
|
We only use libgit2sharp for end-to-end testing. Source Link has its own git data reader. |
Upstream git is actively working on extensions that should be treated as known, even if they are currently experimental, as they do not break these targets.
objectFormatandcompatObjectFormatare used to support SHA256 hashes: https://git-scm.com/docs/hash-function-transitionrefStorageis used to support the newreftablebinary storage backend: https://git-scm.com/docs/reftableThese extensions offer performance and security benefits, and we should expect to see more users trying them out before they become the default in git 3.0.
See https://about.gitlab.com/blog/what-s-new-in-git-2-51-0/#planning-towards-git-30 for details about what may be coming in git 3.0.
Fixes #1097.