It blows my mind that Github still doesn't support stacked PRs. Do they never do work that depends on an open PR? Like, as soon as they open a PR they're like "right, better stop doing anything until it's merged"?

The file priority thing is a great idea too. That would be even more useful for search. The number of times I'm searching for something on Github and it just shows me a gazillion tests.... Yeah you can look up their advanced search syntax and exclude them probably, but it's always a hassle.

▲

steveklabnik 7 hours ago | parent | next [-]

GitHub is putting stacked PRs into private beta around now, actually.

▲

esafak 6 hours ago | parent [-]

link?

▲

bewuethr 3 hours ago | parent | next [-]

https://github.com/github/roadmap/issues/1218 is the tracking issue for it

	▲	IshKebab 19 minutes ago \| parent [-]
		Locked... I'm like 40% sure they'll mess this up in some way that makes it completely useless.

▲

steveklabnik 6 hours ago | parent | prev [-]

https://x.com/jaredpalmer/status/2019817235163074881

(this was a follow-up to the initial announcement months ago, also made via X)

	▲	IshKebab 5 hours ago \| parent [-]
		Ah nice! I hope this actually works across repos rather than just being nicer UI for the existing functionality.

▲

jmalicki 8 hours ago | parent | prev [-]

You can manually stack PRs by making the merge target another branch.

The workflow just makes it a pain, since you have to manually rebase in both the branch and the UI after the original PR merges.

	▲	IshKebab 8 hours ago \| parent [-]
		That doesn't work if the base and PR branch are in different repos, which is the most common way of doing things in Github.