Global Feed Post Login
Replying to Avatar DanConwayDev

Thanks for the update. I'm interested in how you submitted this. if you ran `git push --force` on the original branch (with the name `pr/nip05-lez`), it should have submitted it as a 'revision' to the existing PR instead of a new one. is that what you did? when you originally submitted it did you push with the '-u' flag to link the local branch with the upstream one? potentially there is a bug with ngit here.

Avatar
Lez 1y ago

I think I just ran `git push` - but `push.autosetupremote=true` is set, so no need for `-u`.

Reply to this note

Please Login to reply.

Discussion

Avatar
DanConwayDev 1y ago

The integration test for force pushing a PR is passing so it would be interesting to identify why its not working in your context.

Thread collapsed