After reviewing this exact issue (https://github.com/jupyterhub/binderhub/issues/237) it seems that the functionality for this has been implemented with this merged pull request (https://github.com/jupyterhub/binderhub/pull/671).
However I can not seem to find guidance in the docs or elsewhere which explains what should go into the secrets.yml file or if there are other steps required in order to use Binder with private Github repos (Apologies if I have missed the obvious -- complete Binder noobie here)
Link to my same question in the original issue: https://github.com/jupyterhub/binderhub/issues/237#issuecomment-462711995
The 'Binder (mybinder.org)' part of the OP's question actually refers to two things.
MyBinder.org is a public BinderHub. The issue referenced is referring to Binderhubs in general, i.e., the 'Binder' part of the OP's question. They have set it up and documented how to enable working with private Github repositories on privately-hosted Binderhubs not via MyBinder.org. See the changes referenced by 'docs for private repo access' here.
The discussion in the issue referenced says they won't be allowing that for MyBinder.org.
For access to private repos, you can deploy BinderHub, the software that powers mybinder.org, yourself, or use repo2docker, the tool that turns a repository into a Docker image that will run on Jupyter if you only want to use it locally instead of running a service.
Related
thank you all for taking the time reading my post. I have an assignment where I have to do static analysis for various github repositories. The tool I found is Codacy (I'm open to recommendations though) and I'm trying to see how I can use it using the api it offers. As I was reading the documentation I found out that I can only analyze repositories that I own or I have in my organization but I need it for repositories that are not mine. Do you know if there is another way to get those repositories? I also thought to clone the repositories and creating a private one on my account but I am not sure if it's possible or if it's right to do. I am open to suggestions.
Thank you.
I don't know whether this question should have come in this platform or not but I wanted to ask that let us say I made a github repository which was public. Now another person who has no relation with me downloaded the code, edited it and posted it in play store. I found out that this app which is in play store was my one of the github repositories with some edit. So should I issue a copyright or something or is it fine I should not do anything?
PS: This hasn't happened with me in real. I was just having fear of my repository being used by other but I guess they are so bad that no one would like to use them. Another thing is that pls don't comment that you should make your repositories private.
Any help will be appreciated.
If you are making you repo public you yourself are permitting others to use it. But to prevent misuse of your code and work there are open source licenses available that you can add to your public repo that will put some restrictions on its usage.
More info can be found here:
https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository
https://opensource.guide/legal/
We are migrating the issues of a project from Google Code to GitHub. Google's migration tool assigns all the issues in GitHub to the user GoogleCodeExporter. How can I change issue's author in GitHub?
The GitHub API has a function to edit issues that will allow you to change the assignee (not creator) of the issue. As far as I know, there is no functionality within GitHub to change the creator.
I'm sorry that this doesn't accomplish exactly what you want to do, but it might be the closest alternative (depending on what your project uses issue creator for).
I want to open the issues tab when I open repository because I made a repository just for collecting the tasks for all my project , How can we do that ?
As #VonC has said, this is NOT configurable. It seems that what you require is an issue tracker and not specifically a repository. This articles may help you find an issue tracker that fits your purpose:
http://mashable.com/2014/02/16/bug-tracking-apps/
http://www.thegeekstuff.com/2010/08/bug-tracking-system/
Github's feature for referencing issues in commits automatically just by using the # and referencing commits in issues using the commit hash id is powerful. But is it a maintainable or scalable approach to handle issues from different repositories in one central repository? I do not think so. Issues are important in project development and should be kept organised the same way we keep code clean and organised.
However, this does not mean that it is not possible to maintain your issues in a single github repository. Instead of trying to have the issues tab open automatically, you may create a manual, as a README, for instructions on utilizing the reported issues. This manual will be shown to users visiting the repo. See https://github.com/keybase/keybase-issues as an example. You may find this github article useful in referencing issues.
This doesn't seem to be configurable.
That means you need to open your repo directly at the "Issues" page:
https://github.com/<username>/<reponame>/issues
I am going to release some beta version of my application to the community. Project is stored on GitHub in the private repository.
I would like to allow this community to report bugs and place them directly on GitHub Issues tab - it's not provided by GitHub right now. Do you have any idea, how to cover this flow ?
Not possible as of 2019-09 as documented at: https://help.github.com/articles/issues-only-access-permissions/ (archive):
GitHub does not provide issues-only access permissions, but you can accomplish this using a second repository which contains only the issues.
They suggest that you create a separate public repository just for the issues instead.
Possible same request: Github-like hosting, with private source, public ticketing system
Bitbucket provides this. You can keep the code private but make tracker public (anyone can view, create, and comment on issues).
Use the API access and program some minimal frontend yourself - https://docs.github.com/en/rest/issues