This is the PR: https://tangled.sh/@ilyagr.bsky.social/gitk/pulls/1
Perhaps the problem is that the new branch value is an ancestor of master. (I wanted to test out the PR interface for an already submitted patch)
This is the PR: https://tangled.sh/@ilyagr.bsky.social/gitk/pulls/1
Perhaps the problem is that the new branch value is an ancestor of master. (I wanted to test out the PR interface for an already submitted patch)
BTW, in the original issue post (which I can't seem to edit), I didn't mean to say that the goal was to test out the interface for an already-submitted patch, I meant that I wanted to test out the interface, but forgot that the patch I was using was already in master.
I have a similar problem with a different test PR, https://tangled.sh/@ilyagr.bsky.social/gitk-test2/pulls/3. There, the branch previously had one commit, and the new version of the branch has that same commit and a merge commit resolving some merge conflicts.
In both this case and the above case, the "resubmit" button does nothing.
(I'm not claiming that either is super-important, just playing with tangled and reporting the problems I can find when I throw tricky situations at it).