Azure DevOps - Build Badge - PAT Token not used on private projects · badges/shields#10162

(2 comments) (0 reactions) (0 assignees)JavaScript (22,337 stars) (5,423 forks)batch import

good first issueservice-badge

説明

Are you experiencing an issue with...

My own instance of shields

🐞 Description

Our organisation has strict rules on access, as such anonymous access to badges is disabled.

I have configured PAT token and other Azure DevOps badges work great, the build badges however do not use the PAT token as part of the requests, as such are not able to access the projects.

🔗 Link to the badge

https://shields.io/badges/azure-dev-ops-builds-branch https://shields.io/badges/azure-dev-ops-builds

💡 Possible Solution

Implement fetch using auth (if PAT provided) as other Azure DevOps badges do.

コントリビューターガイド

技術スタック: javascriptnodejsazurerest api
領域: backendapidevops
Issue 種別: bug
難度: 2
推定時間: 1-3 hours
活動状況: fresh
明確さ: clear
前提条件: Node.jsHTTP requests
初心者向け度: 70
調査方針: Examine how other Azure DevOps badges (e.g., test results) implement authentication using PAT token. Look at the Azure DevOps build badge service file (likely in services/azure devops/azure devops build.service.js) and modify the request to include the auth token from the configuration. Ensure existing tests pass and add a test if necessary.