Option to hide deployment history from pull request conversation tab

[vgouv]

Select Topic Area

Product Feedback

Body

When you configure deployment environments with github actions, you can view the deployment history in the actions/Deployments page.
On the other hand this is also present in a pull request's discussion. As this might distract users from following the discussion, there could be a switch (per user configurable) for the deployment to be hidden from the conversation, for users that find this distracting.

[andrijan]

Yes please!

We are currently deploying multiple services on every push. So for each push (If the code changes) we deploy to the same environment. When you have multiple pushes the pull request gets cluttered with duplicate events pointing to the same deployment.

[fokaskostas]

This would be very useful. The PR's UI is very cluttered especially when there are multiple commits

[msto]

Would love to have this feature

[ttbarnes]

This would be great - maybe an option to toggle "show/hide all" would suffice.

[swizes]

This can't be a problem only to few developer. Scrolling takes more time than reviewing the PR -.-

[izaak-gynger]

PLEASE ADD THIS SUPPRESSION FLAG reviews are endless scrolls now and comments get lost.

[jdiponziano]

PLEASE add this, it's driving me insane, i hate the PR interface

[anden-akkio]

I filter out the deployment events with this uBlock Origin rule:

github.com##.js-targetable-element.TimelineItem

Tends to occasionally hide a few other things, but the benefit outweighs the downsides in my usage patterns.

[gmiklich]

Luckily there is a browser extension (called Refined Github) that does this for you, but even if you don't want to use it, you can see the slightly more accurate selector here. Hopefully it helps you avoid hiding the few other things.

[Cellule]

I used Refined Github extension, but it hides only inactive deployments. I really wanted to hide them all.
Thankfully the extension allows for custom css so I used the following to hide more, not perfect either, but a good enough in most cases

.js-targetable-element:has(.TimelineItem-badge .octicon-rocket) {
  display: none;
}

[thatkookooguy]

I hide inactive deployments from timelines in PRs using this css selector with the stylish chrome extension:

.TimelineItem:has(span[title$="Inactive"]) {
  display: none;
}

[OlegMuron]

Hi!

Please add this possibility - it will be an awesome feature!

[gmiklich]

This would be an amazing quality of life improvement when reviewing PRs. The temp deployments provide very little (if any) value to me, and they end up hiding the important conversations that I want to get to.

If github doesn't get around to addressing this, there is a browser extension that allows you to hide such things (among other functionality). I am in no way affiliated with the project, and honestly only found it when searching for a way to hide the messages. Here's a link to the extension (called Refined Github).

[throttlehead-dev]

We're using whats got to be a popular pattern where we do build/canary container tags across workflows, where we build and push the canary tag and then use it in a subsequent workflow as a service that can be tested against. This creates a lot of noise on the PRs and has me second guessing switching GitHub to do our production framework builds as well as that repo is BUSY.

We should be able to disable the output that gets read in prs in the workflow, similar to how you can modify the url:

environment:
	name: prod
	outputToPr: false

[indiarasabarreto]

https://docs.github.com/pt/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests

[oleksiial]

Very needed feature

[yury-dubinin]

Is anyone looking at it? I found multiple treads overs the years with the same ask. Example: actions/runner#2120

[anlandu]

🥲

[Brakjen]

[muchisx]

What's the current workaround for this if it isn't fixed by gh yet?

[brucewroberts]

Use gitlab?

[eirikvaa]

The Redefined GitHub extension can hide them by using the "Hide events" option, but it comes back after a refresh, so it's not really that useful 😬