Hi, Tomas Volf <~@wolfsden.cz> writes:
> Cayetano Santos <csant...@inventati.org> writes: > >>>> What is the standard procedure in codeberg land to travel from a commit >>>> to its corresponding pr ? Same for the other way round. >>> >>> I do not believe there is a way to do that in our model when the changes >>> are merged manually due to GPG signing. >>> >>> At least I see no built-in way to get from the commit[0] to the PR[1] >>> nor the other way around. >> >> #1740 mentions a go and back path between pr and commits. Question is if >> this is valid for all contributors, beyond their status. > > Hm, I have read the pull request description, and I am not sure how > should work. Looking at the pull request #1744, the "Manually merged" > does not seem to be an interactive element. So I am not sure how to > navigate from the pull request to the matching commit. Would anyone > happen to know where I am supposed to click? It looks like one cannot currently search the commit ID to find the associated PR in Forgejo, though it could be extended to do so. There's also this feature request [0] which seems like it'd help. I'm not sure if this shortcoming should hold us back from removing Change-Ids though; the prime motivation for introducing it was having a means to automatically close merged issues in a mail-based flow, not introducing extra traceability. [0] https://codeberg.org/forgejo/forgejo/issues/4247 -- Thanks, Maxim
