[GHA] Clean Stale Dependabot Branches cronjob (3)

[jkoniusz]

[GHA] Clean Stale Dependabot Branches cronjob

CVS-192415

Supporting workflow calls

[Copilot]

Pull request overview

Adds reusable-workflow support to the “Cleanup stale dependabot branches” GitHub Actions workflow so other openvinotoolkit repositories can call it while reusing the cleanup script from this repo.

Changes:

• Exposes the workflow as a reusable workflow via workflow_call with dry_run input and required token secret.
• Adjusts checkout to fetch the cleanup script from openvinotoolkit/openvino (pinned action + sparse checkout), using the current ref for in-repo runs and master for external callers.
• Updates DRY_RUN computation to better handle missing inputs / string-vs-boolean representations (but currently does not allow real deletions for workflow_call).

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[akashchi]

If this workflow is to be used in several repositories, why not transform it into a GitHub Action? It is a cleaner approach when the gha workflow is needed in several repositories. The workflow_call is to reuse in the same repository.

[akladiev]

If this workflow is to be used in several repositories, why not transform it into a GitHub Action? It is a cleaner approach when the gha workflow is needed in several repositories. The workflow_call is to reuse in the same repository.

workflow_call is not necessarily for using in the same repo, there is both a technical possibility and a doc about re-using workflows from a different repo. Custom actions are for being used as a step within a workflow; and this is a standalone workflow, so maaaybe having it re-usable is a better idea

[akashchi]

If this workflow is to be used in several repositories, why not transform it into a GitHub Action? It is a cleaner approach when the gha workflow is needed in several repositories. The workflow_call is to reuse in the same repository.

workflow_call is not necessarily for using in the same repo, there is both a technical possibility and a doc about re-using workflows from a different repo. Custom actions are for being used as a step within a workflow; and this is a standalone workflow, so maaaybe having it re-usable is a better idea

It makes sense, I agree.