[Feature Request]Difficult to understand the branch of the event

[wahapo]

What happened:
When trying to start a detached job, if user accidentally select and start an event that was started from a specified branch, user will not notice the mistake.
Branch filtering

What you expected to happen:
I came up with an idea that it would be nice to have an indication of which branch an event refers to.

How to reproduce it:

[kumada626]

Proposal

If the baseBranch of selected event is differ from pipeline branch, UI shows event baseBranch on event-info area like below.

In this proposal, I think there is a discuss point like below.

• Should UI show branch name if event baseBranch is the same branch of the pipeline branch?

To emphasis the branch is differ from pipeline branch, UI should show the branch name only if baseBranch if differ from pipeline branch.
However, the unified view is the merit of showing branch name always.

Update 2021/08/18

UI should show branch name always even if event baseBranch is the same branch of the pipeline branch.
In other word, branch name column will be added to Pipeline page.

[wahapo]

@kumada626 👍
The branch name should always be visible, in my opinion. If it's not shown, it's a hassle for the user to have to look another headers to find out which branch was build.

[tkyi]

bug: not sure why latest events are missing baseBranch

idea: would be nice if branch was accurate for Pull requests