> But our policy is about all config data, not just push locations. So it > includes the data that you would read when accessing a branch whose > branch.conf you don't control. Indeed, and for that reason I think it's just wrong for branch.conf to ever not be under the user's control. Stefan