badges/shields

Azure DevOps - Build Badge - PAT Token not used on private projects

Open

#10,162 建立於 2024年5月10日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)JavaScript (22,337 star) (5,423 fork)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
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Node.jsHTTP requests
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
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.