
... as seen in:
https://github.com/brianegan/flutter_architecture_samples
This is the currently passing build:
https://cirrus-ci.com/build/6482870825648128
May have something to do with being a first build,... or manual reruns on a task, for example:
https://cirrus-ci.com/task/5753077868003328
Weird since the link points to the right badge: https://api.cirrus-ci.com/github/brianegan/flutter_architecture_samples.svg
I see a green badge in your comment...
Could it be that GitHub cached the redirect when it was failing?
Some mystery of GitHub rendering... Let me poke around... 馃
Seems GH pre-renders Markdown and caches it. Not sure how to avoid it.

Right, I'm seeing

now.
Maybe it rebuilds cache periodically. (I was doing a bunch of re-runs due to transient flutter timeouts about an hour or so ago). Will report back if I see a change.
BTW: I am currently seeing:

in
https://github.com/niieani/bash-oo-framework
which is a first build as of about 20 minutes ago:
https://github.com/niieani/bash-oo-framework/pull/83
@mmcc007 I've switched away from redirecting to cacheble shields to proxying them with no-cache. Should fix the issue but will need to wait for GitHub to invalidate the cache.
FYI:
https://github.com/brianegan/flutter_architecture_samples
is showing the passing badge correctly.
https://github.com/niieani/bash-oo-framework
is still showing the 'not found' badge when actually passing
Seems bash-oo-framework still cached:

brianegan/flutter_architecture_samples also seems to be still cached (if I'm reading this correctly)

But anyway, it's bound to invalidate cache at some point... so I'm not going to worry about it 馃榾
This is happening with me for 5 (five) weeks.
https://api.cirrus-ci.com/github/<USER OR ORGANIZATION>/<REPOSITORY>.svg

@claudioandre-br it seems your default branch is not test so you need explicitly specify it in the URL:
https://api.cirrus-ci.com/github/claudioandre-br/JohnTheRipper.svg?branch=test
Or once there will be a build for the default bleeding-jumbo branch, then the badge will work. 馃憣
Should probably consider using a different image for branches with no builds yet. The image might be a bit non-intuitive for some (like first time users).
For example, travis shows:

and suggests creating a build.
https://travis-ci.com/mmcc007/default_flutter_app
Cirrus provides no similar suggestions (other than a plus sign):
https://cirrus-ci.com/github/mmcc007/default_flutter_app
which may be a little non-intuitive for first time users.
Another option is to use overall the latest build if there is none for the default branch 馃
Or once there will be a build for the default bleeding-jumbo branch, then the badge will work. ok
Another option is to use overall the latest build if there is none for the default branch thinking
There is no "default branch thinking" or I'm still doing something wrong. The default-branch is bleeding-jumbo not master. So:
(no branch info)
(using
?branch=master)
(using
?branch=bleeding-jumbo)
(using
?branch=test)
@claudioandre-br It was still defaulting to master for your repo. Should be working now. Sorry for the inconvenience!