Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Pilot Lvl 1
Message 1 of 9

Workflow/actions status badge giving 404 on private repo in an organization

Solved! Go to Solution.

I tried to put a GitHub Actions workflow badge ony a private repo, however, it's always giving me 404

![](https://github.com/<org>/<repoName>/.github/workflows/main.yml/badge.svg)

Don't badges work on private repos?
The workflow's file is correct.

8 Replies
Community Manager
Message 2 of 9

Re: Workflow/actions status badge giving 404 on private repo in an organization

Hey @Siedlerchr,

 

Thanks for reaching out and for taking the time to submit this report, our engineering team is working on it and I'll post an update here once I have some news.

 


Best,
AndreaG

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Copilot Lvl 2
Message 3 of 9

Re: Workflow/actions status badge giving 404 on private repo in an organization

There is no any information about badges works on private repos or not on Docs. And currently it returns 404

Solution
GitHub Staff
Message 4 of 9

Re: Workflow/actions status badge giving 404 on private repo in an organization

Try replacing: 

 

.github/workflows/main.yml


With the name of your workflow.

 

Path is only used on workflows that don't have a name.

 

Sorry that's confusing. We'll be adding a button to autogenerate these URLs for you in the near future.

Pilot Lvl 1
Message 5 of 9

Re: Workflow/actions status badge giving 404 on private repo in an organization

I tried it today and it works.
Except for linking, it would be nice if a click on the badge would lead to the actions tab.

Copilot Lvl 2
Message 6 of 9

Re: Workflow/actions status badge giving 404 on private repo in an organization

Recently I ran into a similar problem (tried to use the path syntax for a named workflow).

 

But is there a specific reason why we can't we use the path syntax for a named workflow? Some workflows have names with non-English-based, URL-unfriendly characters, and there are cases where path-based URLs look cleaner.

Copilot Lvl 2
Message 7 of 9

Re: Workflow/actions status badge giving 404 on private repo in an organization

I would request to be able to use both name or file path. The name of the workflow might change due to stylistic reasons but the path will most likely (or might) stay the same.

 

Copilot Lvl 2
Message 8 of 9

Re: Workflow/actions status badge giving 404 on private repo in an organization

This solution didn't work for me, I have a private repository that uses the named workflow:

 

 

[![Actions Status](https://github.com/<MY_USERNAME>/<REPOSITORY_NAME>/workflows/Semantic%20release/badge.svg)](https://github.com/<MY_USERNAME>/<REPOSITORY_NAME>/actions)

 

The badge is being displayed, but it always shows "no status".

 

noStatus.png

Highlighted
Pilot Lvl 1
Message 9 of 9

Re: Workflow/actions status badge giving 404 on private repo in an organization

It takes some time until the badge is generated with the correct value.

For me it works now in a private repo