Bypass Camo for private repos #146697
Replies: 1 comment
-
| 🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as  2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the  Thank you for helping bring this Discussion to a resolution! 💬 | 
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Would it be possible to bypass Camo for images embedded in a README (in my case specifically a sonarqube badge) when the repo is private? I have a private repo connected to a private sonarqube instance and I don't see the benefits of running my images for this repo through GitHub Camo, because the proxy will never be able to retrieve the image. However, if one of the developers on the repo were to pull up the README with a direct link to the image it would work just fine.
tl;dr GitHub Camo proxy breaks READMEs using privately hosted images
Beta Was this translation helpful? Give feedback.
All reactions