GitHub Actions badge "Not Found"

I get “Not Found” from URLs I thought would show a build status badge after following the docs here: I have a YAML file with the workflow name “Build” here: The URLs I thought would show the workflow status, or, both return “Not Found”.

Does it take some time for the URLs to return the badge? Or am I doing something wrong?

1 Like

I have the same problem

@hwagit Remove the duplicate <OWNER> name:

whereas you have…

I can confirm the badges do work. 

@rameneI’m not sure I understand you, I have an organization named KikuchiPy with a repo named KikuchiPy, thus the two kikuchipy’s.

Also, I’m not saying the badges don’t work, I’m saying mine don’t work. Or are you saying mine works?

Thanks for reporting this - it definitely looks like a bug.  We’ll investigate.


@codingcrush what’s the repository and workflow where you’re not seeing the badge displayed?

Same issue here : the badge is “404 Not Found” for all my projects using GitHub Actions.
It doesn’t matter if I use the workflow name or its file path.
Some examples:




Sorry you are seeing that. Currently the badge looks for a run passing on the “master” branch. It looks like your workflow runs are on the “develop” branch.

We are looking at letting users specify the branch in the URL so that this use case will work and we’ll update the docs to make that clearer.

My runs pass on the “develop” and “master” branches… but strangely, “master” runs are categorized as “develop”.
It’s probably due to the fact that I use “git rebase” on the “master” branch (so the commit SHA are the same as the “develop” branch).

EDIT: I’ve tried a “git merge” on one of my projects, and it works :slight_smile: The badge is OK, and the run is correctly associated with the “master” branch… but I would like to avoid merging when I can.

1 Like

The badge doesn’t seem to work with my workflow. I am running tests only on PRs. So far, pushing to a branch and then opening a PR launches the tests, but no badge appears after merging the changes.


- The filename is not important

- The Yaml name is the one used

- Name are case senstive! so make sure URL is exactly the casing as ur repo name and workflow name

the badges works fine but you have to have the correct name of the workflow set as the badge name: 

for example 

the yaml file name is main.yml

content must be 

name: main

tags: []

and link will be{{ repo owner }}/{{ repo name }}/workflows/{{ workflow name as in the yaml file and name }}/badge.svg


It works.

But the yaml file name have not to be similar with name: value inside of this file.

Only name: value and workflow name have to be similar.

github actions badge dosen’t work inside a gist.

I was also experiencing that the badge URL was not found. In retrospect, the cause turned out to be obvious, but it is an easy blunder to make, so I’m sharing it here in case it is helpful. In my case, I had just renamed my workflow from the default “Python application” name to a new name. Therefore, there was no badge to be found! I had to force a rebuild by opening a PR. Once I did that, the badge for my renamed workflow appeared.