You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need a GHA to enforce that anyone adding a reusable GHA should have it prefixed with reusable_ this is needed because of a limitation of GHAs where composite actions can live in their own repo (and that should be enforced as well), but reusable workflows have to live in the same repo as other workflows. This is very confusing for people so this naming convention will help people differentiate between what is a local workflow vs a reusable one.
The text was updated successfully, but these errors were encountered:
As part of this, I think that it would be good to have a bool input option for all reusable actions to enable them or not. That way we can sync all of them across all repos and allow repos owners to enable/disable each of the reusable workflows via a config.
Need a GHA to enforce that anyone adding a reusable GHA should have it prefixed with
reusable_
this is needed because of a limitation of GHAs where composite actions can live in their own repo (and that should be enforced as well), but reusable workflows have to live in the same repo as other workflows. This is very confusing for people so this naming convention will help people differentiate between what is a local workflow vs a reusable one.The text was updated successfully, but these errors were encountered: