Is there any way to restrict the release download only to registered users, for a public repository?
No, there isn't. Access to the releases and release assets are allowed to exactly those people that have access to the repository. For a public repository, that's everyone.
If you want to restrict the set of users who can download release assets, you'll need to either restrict access to the repository or use a different solution. For example, if you want to restrict binaries to paid users, you'll need to build something yourself.
Related
is there a way to give a GitHub token only access to pull the latest release from my private GitHub repository. for updating a electron application. I don't want the token to have access to anything else but the latest release only
No, this is not possible. Tokens are generally scoped much more broadly than that (usually to your entire account), and even for ones that are scoped more narrowly, they'd cover at least all of the releases for the repository, if not the rest of the repository contents as well.
If you're trying to distribute software that's in a private repository, you should use some sort of CDN or cloud bucket for doing that (over HTTPS) and implement a suitable digital signature scheme to prevent rogue updates.
I'm trying to figure out, if it is possible on GitHub to give someone read-only access to a specific private repository, allow only to see content, without the possibility of collaboration to contribute with change in the code or readme markup
This is only possible for private repositories managed by organisations.
https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization
If your repository is an organisation one, you can visit:
https://github.com/`OWNER`/`REPO`/settings/access
You can then add a collaborator and set their permission level to:
Read: Recommended for non-code contributors who want to view or discuss your project
Triage: Recommended for contributors who need to proactively manage issues and pull requests without write access
Write: Recommended for contributors who actively push to your project
Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
Admin: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository
I joined a team that has 100+ repositories on GitHub and the watch default setting is ON. I just need it on a handful of repositories. Is there any way to change this setting for all repos without using the web UI and changing it one at a time?
Not that I know of.
In that kind of use case, I would create a second account, and monitor only the few repositories I need from said second account.
That way, I don't have to fiddle with the existing settings for the first account.
I have a hook configured in Github in Organization level which applies all the projects underneath of that organization by default. But I want to eliminate this hook for specific projects of this organization. Is it possible to set up somehow in Github Enterprise?
No, this isn't possible. You will either need to configure the individual repos to have the hooks you need, or have the org-level hook be smart enough to ignore the things it does not need.
Perhaps you can write a simple webhook forwarder that has the logic you need?
Is it possible to give read-only access to private Github project boards? Not to the code projects, just to the boards? The code is for developers but other people in the company should be able to see the status of various projects.
Also, is such access free? I'm setting this up for a small startup and funds are still tight. I don't want to make it expensive for them to get help from friends and family.
You can give access to read or write access to repositories, but it does not provide access like this, but you can look for permission information on this link.
https://help.github.com/articles/permission-levels-for-an-organization/
You can review the article at https://code.tutsplus.com/articles/team-collaboration-with-github--net-29876
We have used waffle in past and it works for providing status only. You can use Waffle for providing the status on different issues https://waffle.io without giving access.