IN PREVIEW: changes to the pipelines page

Announcements
1

We introduced some changes to the way pipelines are displayed on the pipelines page:

  • The column “trigger event” was renamed into “Checkout source”
    This column continues to show the same information as before, but the avatar now consistently shows the profile picture of the commit author, if that information is available. If it isn’t (this is currently the case for OAuth pipelines), the avatar does not show.
  • A new column “trigger event” was added.
    This column shows what event triggered a pipeline (Push, Pull request, API, …) and the avatar shows who triggered the event.

These changes are currently in preview, and additional improvements will be made in the coming weeks. If you have feedback, please comment on this post.

Some known limitations that we are working on resolving:

  • Only GitHub App pipelines show the commit author avatar in the ‘checkout source’ column
  • Pipelines triggered via the UI appear as triggered via the API

image
image2940×1202 255 KB

2 Likes
2

It would be nice to display the name of the human committer in the trigger event column (not only when you hover the mouse over the avatar, but all the time). Sometimes avatars are unrecognizable and you cannot view at a glance who made the commit.

1 Like
3

Hey team, i have some pipelines that triggers 10 workflows, and when that happens the way it is presented is a bit overwhelming as it takes a considerable amount of space and the information is the same for all workflows run.

It seems this could be displayed in the pipeline column, if not an option to hide that column (or at least resize an option to resize it) would be nice.

image
image1767×762 92.7 KB

Thanks for all recent updates!

1 Like
4

@stl-victor-sudakov and @lcssanches, thank you for your feedback.
We will take it into account for fast-follow improvements. I’ll post here when we have updates.

5

@lcssanches actually I have some follow up questions on your remark…
Do you ever trigger pipelines in ways that are not a commit push? i.e. API, manual UI, Pull request etc?
And if you do - do you find it useful in those situations to see that the pipeline was triggered in a different way than a Push?

I’m trying to understand if this information is useful but presented somewhat redundantly, or if it’s simply not useful at all.

6

@Benny, we use mostly commit triggers. We have an API for “ready for review”. In that scenario, it would be useful because that caused some confusion internally in the past. (We couldn’t change to the recent triggers update.)

I think there’s value in that, but the way it is presented seems redundant as you mentioned.

1 Like