This is to reproduce the issue discussed in https://radicle.zulipchat.com/#narrow/channel/369873-Support/topic/Merged.20patch.20still.20appears.20open.20and.20not.20merged/with/562986406
Add a rad sync -i step to check if the issue is caused by the identity document changes not being automatically announced.
Add a rad sync -a step to check if the issue is caused by the identity document changes not being automatically announced.
REVIEW: clean up test into one file
Some additions:
- bob checks the delegates
- bob forks the repository so that
masterisn't new when they push
Changes:
- Adds fix for when delegates merge patches on their first push
- Cleans up the test case and renames it
REVIEW: clean up test into one file
add a rad inspect --refs before and after the rad fork to understand its effect
remote-helper: account for fresh push from delegate
An edge case was found where a delegate attempted to merge a patch,
but had not pushed to their default branch yet.
This resulted in the old not being defined and the check to revert
and/or merge not happening – so the patch continued to appear as open.
Since old only matters for the revert and merge check for the
default branch, resolving the old side does its best to find a
commit for the checks.
It does this by falling back to getting the canonical head before the
push, and using that as the old.
rebase on fintohaps@z6MkireRatUThvd3qzfKht1S44wpm4FEWSSa4PRMTSQZ3voM