4 ms·
GitHub is putting stacked PRs into private beta around now, actually.
by steveklabnik 7mo ago
GitHub is putting stacked PRs into private beta around now, actually.
- esafak 7mo agolink?
- steveklabnik 7mo agohttps://x.com/jaredpalmer/status/2019817235163074881 https://x.com/jaredpalmer/status/2019817235163074881 (this was a follow-up to the initial announcement months ago, also made via X)
- IshKebab 7mo agoAh nice! I hope this actually works across repos rather than just being nicer UI for the existing functionality.
- bewuethr 7mo agohttps://github.com/github/roadmap/issues/1218 https://github.com/github/roadmap/issues/1218 is the tracking issue for it
- IshKebab 7mo agoLocked... I'm like 40% sure they'll mess this up in some way that makes it completely useless.
- l72 7mo agoI just want the simple feature of PRs updating when the target branch changes. For example, say I have two tickets: T-100 and T-101. Both are targeting main, but T-101 builds on top of T-100. I put up a PR for the T-100 branch against main, and put up a PR for the T-101 branch against main. The T-101 PR can't really be reviewed yet, since you are looking at changes from both T-100 and T-101 (because T-101 was based on T-100). Ideally, after T-100 is reviewed and merged, the T-101 PR would automatically update to show only the T-101 changes. But it doesn't. You have to manually rebase or merge main and push changes to the branch to get it to update. It would be great if GitHub handled this automatically.