Show base branch in pull requests list

[driesvints]

Right now, at @laravel, we add the base branch name to every PR so it's obvious to which branch a PR is targeting when viewing a list of PR's. I'd very much would like to see this natively implemented in GitHub so we don't have to do this anymore. The idea would also be for it to be shown in the closed PR list so you have a historical quick overview of PR's and to which (maybe deleted branch) they were sent to.

See the list here: https://github.com/laravel/framework/pulls

What would be cool is if something like the following would be used:

Where the base branch name is part of the item somewhere. This probably needs to be a bit more visually appealing (I'm not a designer 😅).

I'd love for this to be considered ❤️

[Marmok-csgo]

Where the base branch name is part of the item somewhere. This probably needs to be a bit more visually appealing (I'm not a designer 😅).

I'd love for this to be considered.

[driesvints]

Maybe something like this?

[GromNaN]

If you use milestones, they are correctly displayed in the list; and you can also filter on them. You can use a github action to automatically set the milestone from the target branch.

[simonhamp]

But that forces you to create new things just for visual convenience... you already have the target branch, why not show it?

[driesvints]

@GromNaN but that's not the same thing? I need to see the base branch, not some version?

[driesvints]

Talking not only about packages but app projects as well that don't have versioned branches.

[GromNaN]

Let me expand on my thoughts: I assumed that you wanted to see the base branch in order to quickly identify which version a PR is for. Laravel uses 1 branch per major version, and the target branch is chosen according to whether it's a bug fix, a new feature with or without breaking change (I don't know the exact strategy).
From there, you can say that the target branch corresponds to the target version. What I suggest is that you use the tool provided by GitHub to identify versions: milestones.
A milestone is not necessarily an exact version number, it can be a major version number. You might have milestone 10.x for the 10.x branch, milestonone 11.x for the 11.x branch and so on.

[driesvints]

Yeah, I appreciate the thought but just think that's not worth it. We really need GitHub to surface the base branch here.

[driesvints]

In the meantime I've also found this going to be of use on app projects, not just packages with versions. Being able to see the target branch in the pull request view would give me a direct insight in which PR's I'd need to check into.