We are using a public repository (GitHub - netbeez/windows) to distribute our software. Once it’s installed, most uses have automatic updates, so once we upload a new release existing installations kick in their updating process.
What I am trying to achieve:
I’d like to be able to test the updating process before opening it to the public. One way to do that would be to restrict access to our repository to my public IP only, do my testing in our office, and once we are ready, open it to the public.
What might seem relevant (but not quite):
I see that the enterprise plan gives you the ability to manage access by IP (Managing allowed IP addresses for your organization - GitHub Docs) but this is only to manage log in access and not repository access.
Is there way to restrict access by IP to the repositories of our account?
If not, is there another way to do the updating process testing before release?