Github Action keeps running the renamed workflow that no longer exists

[manish-ramrakhiani-eqt]

Select Topic Area

Question

Body

Hi,
I had a Github action workflow that I renamed and now the workflow with the old name keeps running and gets stuck.
I have tried the following.

• I have deleted all the workflow runs from the history but it still keeps happening.
• I have disabled all the workflows but still the old ones are getting triggered somehow.

What could I do to fix this

[felixdiria]

My simple answer to this is.
GitHub Docs

Troubleshooting required status checks

In this article

Conflicts between head commit and test merge commit

Handling skipped but required checks

Required status checks from unexpected sources

You can check for common errors and resolve issues with required status checks.

Protected branches are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud, and GitHub Enterprise Server. For more information, see "GitHub's products."

If you have a check and a status with the same name, and you select that name as a required status check, both the check and the status are required. For more information, see "Checks."

After you enable required status checks, your branch may need to be up-to-date with the base branch before merging. This ensures that your branch has been tested with the latest code from the base branch. If your branch is out of date, you'll need to merge the base branch into your branch. For more information, see "About protected branches."

Note: You can also bring your branch up to date with the base branch using Git rebase. For more information, see "About Git rebase."

You won't be able to push local changes to a protected branch until all required status checks pass. Instead, you'll receive an error message similar to the following.

remote: error: GH006: Protected branch update failed for refs/heads/main. remote: error: Required status check "ci-build" is failing

Note: Pull requests that are up-to-date and pass required status checks can be merged locally and pushed to the protected branch. This can be done without status checks running on the merge commit itself.

Conflicts between head commit and test merge commit

Sometimes, the results of the status checks for the test merge commit and head commit will conflict. If the test merge commit has a status, the test merge commit must pass. Otherwise, the status of the head commit must pass before you can merge the branch. For more information about test merge commits, see "Pulls."



Handling skipped but required checks

Note: If a workflow is skipped due to path filtering, branch filtering or a commit message, then checks associated with that workflow will remain in a "Pending" state. A pull request that requires those checks to be successful will be blocked from merging.

If a job in a workflow is skipped due to a conditional, it will report its status as "Success". For more information see Skipping workflow runs and Using conditions to control job execution.

Example

The following example shows a workflow that requires a "Successful" completion status for the build job, but the workflow will be skipped if the pull request does not change any files in the scripts directory.

[manish-ramrakhiani-eqt]

Thanks. Got the problem. I had set up the workflow as Required on the branch merge policy and when I renamed the workflow, the new name did not reflect on the policy protection rules. It was still waiting for the old name there. This sounds like a bug.
When workflow job name is updated, it should automatically be updated on the protection rules as well

[paulyoung]

I'm also running into this but only the old name is showing up when searching for status checks.

[juanviamonte]

Running into this issue right now

[sarah-carrez]

I had the same issue right now.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬