Move the `failed-workflow` job logic into a reusable workflow

[desrosj]

The failed-workflow job is present in all workflows that run on push events in all branches receiving security updates.

While the logic within the job is minimal, it still relies on a 3rd-party action and backports are required periodically to ensure the job continues working as expected.

The logic within this job should be moved to a reusable workflow in trunk that all other branches can reference. This not only eliminates the maintenance burden, but also allows older branches to take advantage of any improvements made to the logic without needing to backport.

[desrosj]

Marking as a good-first-bug for the first part of this ticket: moving the logic into a reusable workflow.

After this is fixed in trunk, then it can be backported to older branches (which is not so much a good first bug to do).

[atik0130961]

This is a very sensible improvement. Moving the failed-workflow job into a reusable workflow in trunk will significantly reduce maintenance overhead and eliminate the need for repeated backports across multiple branches.

[desrosj]

Hi @atik0130961,

Please leave tickets open until they’re addressed in a commit.

[moisesfonseca]

Reviewed the ticket and patch.
Moving the failed-workflow job to a reusable workflow makes sense given the duplication across workflows.
This should improve maintainability across branches.

[desrosj]

Hi @bsetiawan88,

Could you please open a pull request against WordPress/wordpress-develop on GitHub? That will help validate that the workflow files are valid after applying the patch on this ticket. You'll find some ​guidance around how to contribute using GitHub in the Core Gandbook.

Trac ticket: https://core.trac.wordpress.org/ticket/64298

## Use of AI Tools

[johnbillion]

Alternate approach: ​https://github.com/WordPress/wordpress-develop/pull/11349. Needs testing on a separate repo because it only fires when the workflow is present in the default branch.