Thanks so much for your quick response!
Just curious: would this be something that could be easily supported? I imagine a lot of projects may have several jobs triggered per PR.

why would you not want to see all the checks that apply to your PR?

In my team’s case, we have several parallelised tests that are all in the same group of tests (end-to-end tests). In that same group of tests, there is a separate job that runs before all the tests and it verifies if a review environment (created on each pr) is successfully deployed —otherwise the tests will not run. Not all of these necessarily need to show as they are all part of the end-to-end tests.

Are you asking to just have that area collapsed by default? Or for something else?

Collapsed by default actually sounds like a good idea!
If you look at what we see here (screenshot below), there are only 5 main “checks” we want to keep track of: unit tests, security tests, end-to-end tests, codeclimate, and review environment creation. However, because of the parallel tests you would not be able to see everything at a quick glance.

image861×317 40.5 KB

If I said “how would you like to see this feature implemented”, what would you tell me?

On top of your idea of some collapsible element, grouping/collapsing all related jobs into its workflow would be awesome. Maybe it’s something we can specify in the workflow file? (probably not a good solution but just want to throw some ideas in 😁 )

name: E2E Tests
on: [pull_request]
pr_check_view: collapsed  <--- [collapsed, hidden, display_all_jobs]
jobs: [...]

hi @mickeygousset , are you able to post any update here please? thank you!

Adding on that an option to group or even hide status checks for a given job would be extremely useful. We also run our Cypress end-to-end tests in parallel, so that they’re split across 8 machines:

image922×459 49.3 KB

GitHub automatically creates a new status check for each machine, but we’re really only interested in seeing whether all of the tests passed or failed. In our case, we have a status check set up directly with Cypress that links to the Cypress dashboard (that’s the “cypress: default-group — 2 tests failed” in the image), so the 8 checks created by that job aren’t useful to us.

I’d love to be able to hide (or group) these, e.g.:

jobs:
  e2e:
    name: Cypress end-to-end tests
    runs-on: ubuntu-latest
    checks: none  # or group, or all (default)
    ...

This is definitely something Github should look into it.

We have 80 parallel machines running, so showing each one in the github checks makes it very hard to use.

@mickeygousset any plans to add this feature? We are also facing the same issue when we run the e2e cypress tests in parallel.

Would be great to see this implemented.

Here's a quick & dirty bookmarklet to toggle successful or skipped checks in the list:

javascript:[...document.querySelectorAll('.merge-status-list .merge-status-item')].filter(el => el.querySelector('.octicon-check, .octicon-skip')).forEach(el => el.hidden = !el.hidden)

This may stop working anytime GitHub changes the layout or the CSS classes of that part of their app.

We're working in a mono-repo with 110 checks, so it's extremely frustrating having to scroll and look for the one failed check all the time. Time for this feature to get implemented, @github-staff!

We really need this. Any developer/team that readily takes advantage of GitHub Actions will encounter this problem eventually. The need for it is only going to grow.

https://github.com/EnricoMi/publish-unit-test-result-action#support-fork-repositories-and-dependabot-branches requires to upload the event file, of course this is nothing we want/need to show to the user and is just confusing. So a simple flag on the job
show_status: true/false would be fine.

For Matrix jobs in general, it would be great if only one item is shown for all matrix elements and the can be expanded if needed e.g. lets say I have a Workflow name "Run Buld" with a matrix of jobs "java 8", "java 11", "java 17"

The Github could show one check ("Run Buld") that simply aggregates the status of all childs ("java 8", "java 11", "java 17"), and there is an icon to expand the childs (or one actually can just jump to the job itself)

We're also interested in something, preferably, grouping...

Same situation here! Many workflows trigger a couple of jobs and currently it is a mess to look at them at the status check report

Same here: we have a job generating the matrix for the subsequent jobs.
Nothing tragic, but surely hiding the first job would be nice.

same here, when using things like https://github.com/marketplace/actions/changed-files you don't really care about showing the results of this job in your Checks

I'd also like a way to do this. I have a shared step in some workflows that just builds some values for use in later steps, so it isn't really a "check" on the PR. If one could set something like is_check: false or similar it would be handy.

At the very least for matrix strategies this should be an option, since they are the same job, 2024 and still waiting for this 🥲.

Same problem for my team — cypress run across a matrix job leaves us with 200+ checks in the PR. Would love to have an option to consolidate all the jobs from a workflow into a single check on the PR

Same issue here. Some jobs can be just utils jobs, so showing their result as an extra check is redundant.

Same issue. I agree that the basic use case is to ensure that jobs which run a matrix strategy should only display a single check in the checklist UI. You already have a component for it in showing the progress of a task list for an issue. This circle progress indicator would be perfect.

Next level UX would be to be able to expand the list if you wanted to see individual child jobs.. definitely not a need to have.

The details link can just link to the first job as you end up seeing all the jobs in the side bar anyway.

Who at github wants to give me a codespace to github's webapp and I can ship this in a week?