Azure Pipelines status badge doesn't show up
See original GitHub issueI was able to figure out that if you’re not logged in it gives an error as the response. If I hit the pipelines page and get logged in, then I can see the badge.
{"count":1,"value":{"Message":"Build pipeline BrandonPotter.GoogleAuthenticator was not found."}}
Any ideas, @flytzen ?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Azure Pipelines status badge not getting displayed in ...
You can go to Project Settings, click Settings under Pipelines. And make sure toggle Disable anonymous access to badges is off. Please refer...
Read more >Azure DevOps status badge settings not loading
When trying to create/read a badge for my project, it shows "setup now" in the badge if I build my own url, and...
Read more >Add status badges for your GitHub repo - Azure Boards
Select Status badge and then check or uncheck the Allow anonymous users to access the status badge. When it's unchecked, users who aren't...
Read more >Fix Build status badges · Issue #562 · debauchee/barrier
The reason that your build status badges aren't working is probably due to the fact that you're running all builds in a single...
Read more >AzDevOps Tutorial: How To Show Your CI Pipelines Status ...
You can show your Azure DevOps Build (CI) Pipeline status badges in markdown (.md) file in any your public or private repository such...
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
Changed to public, check now?
While we’re making changes to the project there, I propose disabling the approval check since at least three versions now have not been approved to be pushed to Nuget (timeouts after 30 days).