Is it possible to 'symlink' to a github repository? That is, have a github repository at github.com/user1/symlink_to_project seamlessly point to github.com/user2/another_project? The use case is an organization that wants to link to an existing project that already has numerous issues, stars, etc. I'm not sure what the proper term for this would be in github parlance, although I've searched for mirror, link, etc.
It's not possible to "symlink" a repository, but likely what you want to do is transfer the repository to an Organization account.
More info here: https://help.github.com/articles/transferring-a-repository/
What's transferred with a repository?
When you transfer a repository, its issues, wiki, stars, and watchers are also transferred.
that's basically what git submodules are: https://git-scm.com/book/en/v2/Git-Tools-Submodules
you can do it, but if you are going to use submodules you are usually going to have a bad time in the long run.
Related
We are a small team doing our own project and we need to somehow add a repository to each participant, so that later we can show what we did, how can this be done correctly?
We tried to google but did not really understand how to do it, leaving just a link like 'I took part in this project' seems to us not such a right decision
You need to set up a central, bare repository and have everyone clone that. Then they push and pull from that central repository to stay coordinated. There are various workflows of which the feature branch workflow is a good place to start.
Rather than doing this yourself, it's much simpler to host your code on a service such as Gitlab or Github. Both offer private repositories for free and many, many excellent additional features.
We have hired a 3rd party to work on a project, we started by not creating any Repo on our Github, but they started with their Repo. So now it's time to transfer the repo. However, in order to transfer the repo, the developer is asking permission to create a Repo in our Org... but as far as I know, I can only invite him first as a collaborator, a member, before he can create any private repo in our Org... that means he can see our other repo...
I couldn't find any good answer online, please help. Thanks!
Have you tried using Github's Organization features? You can create an organization with your team members in it, and control who has access to what.
Here's a Github page that explains a bit more about how it works.
Do not add them as a member to your Org! (this is the only option today from Github, nor owners...of course). If you do so, this will give your external developer access to all of your repos.
The only way I found you can safely invite an external user is to create a Repo first, then add them in that Repo. By doing that, they will be invited only to that repo, and have no access to the others.
This is my workaround. If you have a better solution, please do comment. I am curious how the "transfer" feature works.
I've almost done my first big project in React+Typescript+Redux and started it on Firebase with users and some database conneted with logged users.
It was supposed to be my project to portfolio before looking for my first dev job, but it start to be very complex.
Now I have idea to use it in the future to make commercial app.
So the problem is I don't want to publish my code on github, but at the same time I want to publish all my commits and repository description on Github for recrutiers (and all my tasks from trello table). Is it possible to publish only commits and description from github repository?
No, this is not possible. If your repository is public, anyone can clone the entire repository. The only way to make your code inaccessible is to make the repository private, which means nobody can see it without having permssion.
My company wants to contribute on opensource projects and managers want an easy way to see which upstream issues were closed by forks from our organization.
Is there any way to maybe copy upstream issues to a fork or reference them in an easy way to track my organization contributions to a project?
This may be possible through GitHub Projects. Projects exist per the organization, not a particular repo. You can also link to issues and pull requests from repos of other organizations by entering user/repo#issue in the project's task description.
In the case of your scenario, suppose your team shares a GitHub organization. You can create project, then add items that reference your issues and pull requests, which exist within the open source project's repo. You can configure and organize your project's view(s) to display the information you want to show. Since this merely links to the issues/PRs from the open source repo, the original stays intact, and how they are displayed in your project stay in sync.
This has baffled me for quite a long time.
I notice that anyone with a link can download the repository. But the question is, where do they get the link from? I cannot seem to find a page on GitHub listing all the newly published repo.
Everytime I publish a new repo, there would be 3~6 mysterious clones follow shortly after, even when the number of visitor remains at most 2 persons.
While I welcome people to find out what my code can do, it somehow gives a pressure on me not to publish unfinalized code, and also not to amend the content of my repo after publishing it because they might already have cloned it before the changes are made.
Alright, it has 2 visitors (including me) to be exact:
You have no way to see who has checked out your repository using standard git commands such as git clone, but you can see who has forked your repository on GitHub in the Traffic section under Insights.
Now my first thought would be that those people cloned your repository outside of Github as you don't need to be a Github user to clone repository (so Github couldn't keep track of them and you wouldn't be able to see them).
Good luck, hope this helps.