Required checks not passing for reusable workflows
See original GitHub issueDescribe the bug Required checks do not pass for reusable workflows
To Reproduce Steps to reproduce the behavior:
- Create a status check for a job name (ie
pipeline
) - Create a reusable workflow with a job similar to the required check (ie.
pipeline
) - Create a new workflow using the reusable workflow
Expected behavior The required status check should acknowledge the workflow run
Runner Version and Platform
Version of your runner? 2.292.0
OS of the machine running the runner? Linux
What’s not working?
The workflow runs but the required check is still waiting:
The required check is docker
. The job in the reusable workflow is docker
. The job that calls the reusable workflow is docker
.
Issue Analytics
- State:
- Created a year ago
- Reactions:21
- Comments:12
Top Results From Across the Web
Required checks for PR do not run when workflows ...
The issue is that when I make a PR to main, the test workflow runs and completes, but the other checks never finish...
Read more >How to start using reusable workflows with GitHub Actions
When combined with OpenID Connect, reusable workflows allow you to require certain tests to be run before code can be deployed to production....
Read more >Github reusable workflows and how to verify them - Europace
First off, the reusable workflow was modified to allow checking out a different repository. This requires allowing to pass in the repository ...
Read more >Avoid Duplication! GitHub Actions Reusable Workflows
Note: if a required input has not been passed to the reusable workflow, it will fail. Other available types are boolean and number...
Read more >GitHub Actions fails to fetch secrets within reusable workflows
Secrets need to be passed from within the parent workflow. There are two ways to solve this: 1. Explicitly add secrets to the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just got into this problem today, the reusable workflow seems to have name constructed as
<parent_job_name> / <reusable_workflow_name>
but when I want to use that for status check it is not possible to find itRan into this too. Why is it not possible to have reusable workflow as a requirement check for merging into master? This is absolutely basic functionality. Why then even have reusable workflows when I can just shove it all into one insanely huge yAML to work around this?
🤦♂️ I am regretting ever having to use github actions. We can now write a book about how terrible it is.