Option to mark reusable workflows as templates to not show them under the "Actions" tab

[aramfe]

We use several templates for our workflows in form of reusable workflows, that we never call for themselves, but only call as reusable workflows.

There should be an option to mark/hide workflow files as reusable workflows, to not show them under "All Workflows" as it is the case right now.

[ethomson]

Yes, I agree that this would be a useful improvement. Thanks for the feedback.

[pbarhyl]

Any update? We have empty workflows what only distracting us from main content.

[ssbarnea]

I think that this could be implemented by adding an implicit filter to "All workflows", and that would not only allow us to hide these but also control which actions we want to not be listed in the default views.

IMHO, that approach is more flexible and allows full control for the user to hide/show actions that are relevant to most users.

The current situation is that other workflows, liked ones that run on any issue edit, including label changes are cluttering the UI. Example https://github.com/ansible/vscode-ansible/actions

[v4hn]

665 question upwards and going. Pretty please?

I have a rather weird situation right now that hints at something going wrong behind the scenes.
There are four workflows in the repository and two of them are exclusively reusable workflows.
For some reason one of these two reusable workflows shows up, but the other does not.

I would expect that the UI does not show any workflow that only specifies the on: workflow_call trigger, as nothing useful can be done with them in the UI.

[ChromeQ]

665 question upwards and going. Pretty please?

I have a rather weird situation right now that hints at something going wrong behind the scenes. There are four workflows in the repository and two of them are exclusively reusable workflows. For some reason one of these two reusable workflows shows up, but the other does not.

I would expect that the UI does not show any workflow that only specifies the on: workflow_call trigger, as nothing useful can be done with them in the UI.

I disagree that there is nothing useful from workflows without the on: workflow_call. I often want or need to look at the logs for automated actions triggered from PR merges or failures from a test run which was triggered from a commit or newly opened PR.
Manually triggering a workflow is not the only "useful" situation to be able to see.

[v4hn]

I disagree that there is nothing useful from workflows without the on: workflow_call.

That is not what I wrote. If a workflow only specifies the on: workflow_call trigger and no other trigger, it can only be invoked through other workflows and will never list any runs (and thus no logs) for itself on the website. Thus it's entirely useless to have a website that lists all runs of this workflow with the option to sort/filter/search through them.

I often want or need to look at the logs for automated actions triggered from PR merges or failures from a test run which was triggered from a commit or newly opened PR.

Everyone does.

[bnlf]

+1 to this. The UI for Actions is already bad enough and not able to hide reusable workflows is very annoying.

[Sxnan]

+1 to this. Having the reused-only workflow in the tab is distracting.

[samwisekind]

I'd be super keen for this too! I tried burying the reused workflows at the bottom of the list but unfortunately doesn't seem easily possible due to the way the list is sorted. Maybe it should hide the workflow if it only has on.workflow_call?

[razdrom]

+1

[LPauzies]

+1 to this !

[cbarbosa2]

+1

[matiza5]

+1

[muzahm01]

+1

[Vana12330]

Ми використовуємо кілька шаблонів для наших робочих процесів у формі багаторазових робочих процесів, які ми ніколи не називаємо самі по собі, а лише називаємо багаторазовими робочими процесами.

Має бути можливість позначати/приховувати файли робочих процесів як робочі процеси для багаторазового використання, щоб не відображати їх у розділі «Усі робочі процеси», як це відбувається зараз.

[pbarhyl]

+1

[flaxel]

Please use this GitHub feature to show that the feature is important, but please don't write +1 every time.

[prashantkumar-tomtom]

+1

[martindevnow]

+1

[prein]

It could be a generic hide/show switch, rather than logic checking if the workflow is reusable without other triggers. More flexible and less error prone.
Consider for example

name: foo
show_in_ui: false
on:
  workflow_call:
    inputs:
    ...

[polo4096]

+1

[vmikhalskyi]

+1

[gorgice]

👉 👈

[justadevopsguy]

+1

[Sheludchenko]

+1

[ranma2913]

Having to prefix my workflows annoyed me enough that I decided it's less work to move all reusable workflows into a separate repository.

My reusable workflows repo only has those reusable ones, so then I don't care if they show up in the actions list there, in my application repo there's only my leaf or trigger workflows so no more issues.

[kriehzoo]

Could you pls give us an update on when this will be available?

[lucasingels]

+1

[stmaute]

Any news regarding the feature?

[Manbearpiet]

Would love to have this, hope it can be implemented soon.

[real-marshal]

too hard to implement i guess.. maybe hire me

[SivkovSavely]

☝️ Hire him

[dawsayan]

Any update?

[LanusseMorais]

+1

[aramfe]

OP here:

Wow. I switched to GitHub Actions four years ago. Back then, I never thought a small feature request would get this many likes and still follow me in my email notifications after FOUR YEARS—and is still not implemented.

I can surely flex in interviews that I created a feature request for GitHub with 1,000 likes.
Just need to make sure nobody asks what the request specifically was 🤣

[Eniadebisi]

The option to visually hide it too would be nice. Under the "Show more workflows" which is already implemented.. make easy job easier eh?