GitHub Community
Hide Jobs in Actions UI when If is false #18001
Replies: 80 comments 13 replies
-
|
This is really desirable!! |
Beta Was this translation helpful? Give feedback.
-
|
The default behavior should be that skipped jobs are hidden. If someone wants to see the skipped jobs, let them optionally enable that. |
Beta Was this translation helpful? Give feedback.
-
|
Whenever this is implemented, Please make it optional. |
Beta Was this translation helpful? Give feedback.
-
|
The default behaviour should be rather that skipped jobs are shown. It would be less of a breaking change to introduce a new job option |
Beta Was this translation helpful? Give feedback.
-
|
Any update on this? I'd still very much like to hide skipped actions on PR's in the UI. |
Beta Was this translation helpful? Give feedback.
-
|
Not exactly a "solution", but I personally installed Tampermonkey and wrote a very much not-ideal but better-than-nothing-for-me script to hide them for myself: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @DanCardin, Click to expand!
|
Beta Was this translation helpful? Give feedback.
-
|
Up: Got it working with the following - thank you @DanCardin! // ==UserScript==
// @name foo
// @version 0.0.1
// @match https://company.com/myorganization/*/actions/runs/*
// @description baz
// ==/UserScript==
(function() {
'use strict';
setInterval(removeSkippedJobs, 1000);
console.log("Filtered Skipped jobs!");
})();
function removeSkippedJobs() {
document.querySelectorAll(".merge-status-item > .merge-status-icon > .octicon-skip").forEach(
(node) => node.parentElement.parentElement.remove()
);
document.querySelectorAll(".ActionListItem-visual > span > div > .octicon-skip").forEach(
(node) => node.parentElement.parentElement.parentElement.parentElement.parentElement.remove()
);
} |
Beta Was this translation helpful? Give feedback.
-
|
Bump! This would be great! Keep in mind that Slack will show it as grey when it is much more desirable not to have this notification at all! It makes the actions look quite busy when in fact, they either pass or fail.
|
Beta Was this translation helpful? Give feedback.
-
|
Bump! Also adding a use-case for this feature. I am using "proxy workflows" as a workaround for a lack of dynamic "uses" when triggering reusable workflows (choosing which to execute). I am using a solution similar to this suggestion. The problem is that every use of the "proxy workflow" results in skipped jobs showing up due to the A job-level setting or even a UI setting would be helpful in making this a better experience. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Maybe an easier/less invasive option would be to extend the java-build:
name: java-build
needs:
- metaconfig # job
- ${{ jobs.metaconfig.result == 'success' }} # job resultThis would effectively hide the skipped jobs but would require an evaluation of boolean as well as a job_ids in the |
Beta Was this translation helpful? Give feedback.
-
|
This problem is significantly worse when using Matrices and/or reusable workflows. In the below image, we had one reusable workflow that can take one of three journeys down the remainder of the workflow logic. The other three paths (and their sub-paths) are shown in the UI and often cause confusion. |
Beta Was this translation helpful? Give feedback.
-
|
We also make heavy use of shared workflows with switches to turn workflow features on and off. I'd love to see this feature added. As a workaround, we use the following pattern which allows some ability to distinguish between a step not being enabled, and it being skipped for other reasons. One note is that if you use a step outcome/output in place of the enable input here, it will still work. But the formatted string will not be evaluated until the job completes. While the job is running, the code that generates the name will be displayed. |
Beta Was this translation helpful? Give feedback.
-
|
I would like to +1. In my case I have a reusable workflow inside a matrix, and one of the job of the reusable workflow should run only in some cases, after other jobs in the reusable workflow. A job-level setting would be great to hide those that don't run. |
Beta Was this translation helpful? Give feedback.
-
|
+1. Definitely a needed enhancement to GitHub Actions UI. At least have a UI option to hide skipped jobs. |
Beta Was this translation helpful? Give feedback.
-
|
+1 it would be great the have the option! |
Beta Was this translation helpful? Give feedback.
-
|
+1 Bumping up, would love to see this feature! |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1, would be very cool if we could hide skipped jobs! |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
👋 Hey folks! I created a userscript that hides skipped jobs in the actions UI. I've been using it for well over a year (don't let the commit date fool you, I just cleaned up my local code and made the repo public) to my enjoyment. ⚙️ Repo w/ Installation Instructions: 👉 https://github.com/ChrisCarini/github-hide-skipped-jobs-steps-userscript
Give it a try, and feel free to suggest any improvements (PRs or otherwise) in the repo itself! Best, |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
-
|
Did you happen see my comment above and give the userscript a try? I'd love to hear your thoughts & feedback! |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately not. This is an issue at work, and unfortunately we cannot install the extension which will enable that. |
Beta Was this translation helpful? Give feedback.
-
Ahh, bummer! I can understand that. Just so I can get a better sense, would your workplace be more open to it if it were a separate/standalone browser extension? |
Beta Was this translation helpful? Give feedback.
-
|
TBCH I don't know. If i were to take an educated guess, I'd say that extensions of this type are just going to be denied straight away. It's a very long process to even request review so I have no appetite or time to explore it. |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha - yeah, I can sympathize with long review processes for stuff like this (I've been in similar situations). Welp - sorry my 'solution' won't work for you. Hopefully the GitHub team can come up with something that works nicely for everyone here. 🤞 |
Beta Was this translation helpful? Give feedback.
-
|
+1 !! |
Beta Was this translation helpful? Give feedback.
-
|
Did you happen see my comment above and give the userscript a try? I'd love to hear your thoughts & feedback! |
Beta Was this translation helpful? Give feedback.
-
|
The more I use GitHub Actions the more basic features I find are missing. Showing jobs that are conditionally skipped is such a bad design decision. It makes designing reusable workflows a mess. I should not have to maintain separate workflows with different jobs just cause I want to hide something from the UI. I have hundreds of repos I need to do CICD from and l want to use 1 centralized reusable workflow that everything is nested under. This way I can decouple jobs into independent reusable workflows nested in a root workflow. So all my repos just have to reference 1 main reusable workflow that conditionally runs jobs depending on that projects needs. |
Beta Was this translation helpful? Give feedback.
-
|
It's almost like Microsoft bought Github so they can reduce the support to nothing so that people switch to something else. |
Beta Was this translation helpful? Give feedback.
-
|
I don’t think Microsoft is trying to push anyone to Azure DevOps. They haven’t added any real features to ADO since 2019. Plus when you have a GitHub Enterprise account you can use Azure DevOps at no extra cost. When I went to AWS ReInvent this past December and spoke with some people at GitHub it seemed their strategy was to go all in on GitHub since it’s seen as cloud agnostic and essentially is the open source community. Cause AWS products for SCM and CICD suck but most people who use AWS don’t want to use Azure DevOps, so GitHub has a good position by comparison. It almost seems the only reason Azure DevOps still exists is the legacy customers and people who originally use VSTS that stick with a Microsoft stack. It seems the focus on AI features has distracted them from some basics. It also does not seem like they have an interest in CD features, the entire environments feature needs a lot of work. I’m migrating hundreds of CICD pipelines in GitLab to GitHub. As much as I hate GitLab cause they’re unstable and break things to often with “feature” updates, at least they have a good variety of features at no extra cost. Like code scanning for secrets. GitHub making that an extra paid feature is stupid expensive, total cash grab. And the recent announcement to charge people for self-managed runners that they had to walk back due to the backlash. So you’d think they’d have more incentive to build out robust CICD features. I don’t get why they’re dragging their feet on this stuff. |
Beta Was this translation helpful? Give feedback.
-
|
+1 |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
-
At time of writing this when you have a multi-stage workflow defined it will show every single job and set of steps defined in all associated workflows and composite actions. Having the ability to hide a job in the UI if it will not be ran would be a great feature.
Examples of this are build testing, integration testing, code scanning, and security scanning. There are times when they will not be ran and having them show up in the UI really clutters it up.
Current Workflow Example Below in the UI
Current Workflow Example Below in the UI
Beta Was this translation helpful? Give feedback.
All reactions