I see that the visibility of maintenance branches like release/17.4.1 or release/17.5.0 is restricted. That makes it impossible to test packages based on them before they are released again. Specifically my PostgreSqlProvider package is critical for "internal" changes in raw sql. I have already experienced that the awareness of proper use of the persistence layer is quite low. Luckily Andy promised to have an eye on this during code reviews. But there might be cases that are not that obvious. Actually I do not see why these branches are hidden as they are already protected by PR merges and required review policies. Maybe there is a way that I do not know, how I could get access or any other idea / advice how to handle this? 😟

Hi Dirk, not aware of any specific rule to hide release branches, and at least, that is not the intent. Could you share a few more details as in what you expect and what you currently cannot do?

Hm, maybe this was only an issue in Visual Studios Git implementation. Trying to make screenshots to explain the issue, I used another tool to fetch the upstream of my fork and now I see the release branches. 🤔 So all is good.😊 I'll try to investigate this further and share my findings - just in case someone else stumbles across it.👀

Nice 😊