One of our users create a private repository within and organisation on GitHub Enterprise. He added a collaborator, but this person get 404 error when trying to access the repo. I added my account to this repo and all works fine for me.
Added collaborator is in the same organisation, repo is visible on his profile, link to repo is fine too (it works for me and repo owner).
I was searching the answer in Internet, but no luck.
Do you have any idea, what can cause this situation?
This usually happens because the user who is having an issue's client isn't properly authenticating.
You can read more about it here: https://developer.github.com/v3/troubleshooting/
Related
I changed a GitHub repo from private to public and it gives me this error when trying to push changes from the terminal:
ERROR: Repository `user/repo-name' is disabled.
Please ask the owner to check their account.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I can still view the code and make commits but it won’t push the changes. I also am not able to fork the repo - it says that “Cannot fork because repository is locked”. I already have my SSH key working on GitHub, which was the only answer I’ve found when researching this. Everything worked fine before I changed the repo from private to public. Any suggestions?
Contacted GitHub support and they unlocked the repository. It may have happened because I changed the repo from private to public during their outage. Everything works fine now
I am the owner of a private GitHub repository. Somebody else (student1) forked it a while ago and has done some work on his fork. Now I need somebody else (student2) to pull those changes and work off of them. However, he cannot access student1's fork at all. Trying to git pull provides an error about not being able to find it. Student2 can also not see student1's fork on GitHub's website.
Everybody is added as a collaborator. I can access all forks (I am the original owner of this repository). I tried removing student2 and adding him back but it changed nothing. I tried inviting another friend (let's say student3) and he can fork but also cannot see other forks. In the past, I distinctly recall any users added as collaborators being able to pull from other forks so I am not sure why this isn't working.
All I see is "Find another repository to fork"
You can fork any private repository you can access to your user account or any organization on GitHub Team or GitHub Enterprise in which you have repository creation permissions.
Maybe this is possible through an organization, where you can change member privileges.
So, my question is:
How to access private repositories of Bitbucket/Github or any other online web-based version control repository hosting service.
Any feedback is most welcome.
Thanks
Steve Washer
I'll only speak for github as a daily github user. The only way to access them is either by being member of the repository or outside collaborator of the repository. Owner of the repo can add you to it in the repository Settings.
Another way is to ask any of the members to provide you the personal access token, which you could use to read the repository via the API. This is however, unsafe.
Yet another way is asking the repository owner or any repo user to add your public SSH key to his account so you may have repo access (clone, commit) without ability to view it on github.com
Summary: you always need to talk to the owner or any of the current repository members. Private repo will never be accessible otherwise.
We have a private repo in our org on GitHub and I've invited some external user to this repo. I have him the "Read" access. He can now read and clone the repo (I guess the clone will stay private, right?).
What can he do inside issues?
According to the documentation of the permission levels a collaborator (inside or outside of the organisation) can:
> Open, close, re-open, and assign issues
Haven't tried it out. But it sounds meaningful to me.
I am curious if I can add a collaborator for just watching my project without giving him the rights to make it public, yet.
So, the current situation would be:
- I created a private GitHub repo that I don't want to have public yet
- I have a colleague who does not have a paid GitHub account
- I want to add this colleague as "watcher" only without exposing the project to the public yet
Would that work?
Assuming you trust your collaborator to not clone the repo and post it publically, yes you can add them as a collaborator to see the private repo.
From Github's docs: "All collaborators must have GitHub accounts. It's easy to sign up, and even accounts on the free plan can collaborate on private repositories"