I’m confused by how pushing to new branches would work on GitHub (or is the point that it doesn’t…)?
Are you able to change the branch of a PR from `v1` to `v2` without making a new PR?
Yes, the point is that it basically doesn't support that.
Well, OK. You can push two branches, v1 and v2, each with the commits. Then to do pairwise diffs, you type in the commit object hashes directly into the URL bar to diff the two objects in the repository using the 'blobs' API but like... I don't think that qualifies so much as "supporting" it as much as an absurd hack, right?
> Are you able to change the branch of a PR from `v1` to `v2` without making a new PR?
Whenever you force push v2, v3, v4 of your branch called "foobar", you can also push branches called "foobar-v2", "foobar-v3", "foobar-v4" (pointing to identical commit hashes, respectively). The "foobar" branch is what refreshes the PR. There are no PRs for the versioned (and effectively read-only) branches, they are there for reviewer reference.
aseipp|1 year ago
Well, OK. You can push two branches, v1 and v2, each with the commits. Then to do pairwise diffs, you type in the commit object hashes directly into the URL bar to diff the two objects in the repository using the 'blobs' API but like... I don't think that qualifies so much as "supporting" it as much as an absurd hack, right?
> Are you able to change the branch of a PR from `v1` to `v2` without making a new PR?
No, you have to open a whole different PR.
another-acct|1 year ago
planetpluta|1 year ago