As another thinking out loud idea, I was wondering...
# feature-requests
r
As another thinking out loud idea, I was wondering if the graphite team have considered storing the
parentBranchRevision
ids directly in a ref (e.g.
.git/refs/branch-metadata/my-branch/parent-base
instead of a json file so that it could integrate with the
--update-refs
feature that's in Git 2.39, so then if people where to use
git rebase --update-refs
(or if they enable updateRefs globally) that could be compatible with graphite?