Add helpers/stale-issues as an action #105
Conversation
There's currently a reusable workflow for marking issues as stale. This adds a reusable action, which allows for running the task along other helpers (e.g. most likely helpers/lock-issues) on the same runner and with a bit more flexibility than what can be achieved with the workflow. The inputs and steps stay the same as in the workflow.
sairon
changed the title
|
|
||
|
|
||
| runs: | ||
| using: "composite" |
There was a problem hiding this comment.
What is the reason we add this as a "composite" action instead of using the syntax for reusable workflows?
https://docs.github.com/en/actions/using-workflows/reusing-workflows
There was a problem hiding this comment.
The goal is to use it in the same way as lock-issues (added in #104) and other helper actions - the stale job implemented as a workflow is an outlier and doesn't bring any extra benefits IMHO. So far the workflow is used only in in three repos so getting rid of that shouldn't be a big challenge now.
There was a problem hiding this comment.
Also home-assistant/helper/stale-issues@master is a bit less clumsy than home-assistant/actions/.github/workflows/stale.yaml@master.
There was a problem hiding this comment.
I think #104 should have been a reusable flow as well (like stale.yaml), as that is not really a helper.
That one, and this PR is adding standalone actions, they are not really like the other helpers in this repository.
composite actions are designed to be a step in a job, for all these 3 they are meant to be the entire job.
There's currently a reusable workflow for marking issues as stale. This adds a reusable action, which allows for running the task along other helpers (e.g. most likely helpers/lock-issues) on the same runner and with a bit more flexibility than what can be achieved with the workflow. The inputs and steps stay the same as in the workflow.