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.

[nmargaritis]

What's the status of this? We currently have about 10 reusable workflows and 3 main flows for each env. It would be good if reusable workflows were placed under a different tab such as workflow templates or not show up at all. They are not triggered and can't be triggered anyway....

[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

[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:
    ...

[P1119r1m]

Here's what GitHub Action looks like in product for our team members:

The Collapse/Expand option "Show more workflows..." made user experience even worse.
Let me note that most of the useful workflows are hidden in "Show more workflows....".

Hey, @github!
Don't you sometimes want to hire at least one employee who understands user experience for your company? :)

[h2oearth]

looks familiar :-/

[ja-leo]

2024 and we are still here, please allocate one dev a week to implement this small UI feature

[higordearaujo-bsy]

@ja-leo @P1119r1m @h2oearth @troyere

There are some workflow UI changes on the roadmap which seem to be scheduled to land in late march / early april:

The UI changes will include a search box for the list of workflows, the ability to pin a workflow to the top of the list, indicators to separate out disabled workflows, and other improvements for readability.

github/roadmap#841

[sombriks]

+1, joining the reusable club and my boys will get really confused if thy need to run something by hand because of this

[isaac-smothers]

+1, would love if this was implemented

[oleksandr-danylchenko]

I'm shocked that it still hasn't been added 🤯

[takano32]

I wanna use this feature, too.

+1

[andyhinds]

+1 fwiw

[gsmith-idexx]

+1

[JustinJohnWilliams]

Seems to be a lot of support for this feature, any word on roadmap?

[h2oearth]

For all the +1 remember this https://github.com/orgs/community/discussions/12025#discussioncomment-3978445

[FearlessHyena]

It's been 2 years since the original comment so at least some form of response from @github on if this will/will not be implemented would be appreciated at this point

[mandeepsingh-dh]

Any update on this? It's taking way too long to implement a simple but important feature

[eadmundo]

I 100% agree this would be a great feature, but in the meantime the way we work around it is to create actions in the same repo and use those instead of reusable workflows: https://docs.github.com/en/actions/learn-github-actions/finding-and-customizing-actions#adding-an-action-from-the-same-repository

[Sojaner]

I have noticed that the team has solved this issue in another way and think that's also smart.
Since a little while ago, I've been able to pin the workflows that I want, to the top of the list of the workflows.
I like this approach since we don't need to change the workflows and it's quite fast to pin/unpin the workflows.