![github desktop forked repository github desktop forked repository](https://dl.flathub.org/repo/screenshots/io.github.shiftey.Desktop-stable/1504x846/io.github.shiftey.Desktop-f95c55694c1fe8e6c474d34b66706af2.png)
We want to link them together to synchronize them and share our project with the world. Now we’ve created a remote repository on GitHub, but haven’t made a local copy yet. In the previous episode we created a local repository on our own computer and pushed it to a remote repo on GitHub. We do not need to do any of that for now. GitHub will also ask if you want to add a license or a. Check the box for ‘Initialize this repository with a README’.Give it the name github_ (replace ‘github_username’ with your GitHub username).Click on + icon on the top right of the site.When we have logged in to GitHub, we can create a new repository by clicking the + icon in the upper-right corner ofĪny page then selecting New repository. This feedback is private to you and won’t be shared publicly.Link a local Git repository to a remote GitHub repositoryĮxamine the difference between an edited file and the file’s most recently committed version Mark contributions as unhelpful if you find them irrelevant or not valuable to the article. For instance does a tool offer to show blame info or does a tool offer integration of side by side views. What I saw, is that there are some detailed feature that could decide. If now someone is just interested in using a Git tool to compare history, it is is really a matter of personal taste. With having all three features, my first choice is Fork. I have a working directory where I have repos and so far the only tools that seem to provide that is Tower and Fork. I love the idea of a Repository Manager, because this is what I am looking for. But still for my very personal way of working, there was one tool that stood out a bit: Fork. My personal recommendation: ForkĪs written above, different ways of of working, different recommendations. People seem to like GitKraken for its DarkTheme (really is that so important).
![github desktop forked repository github desktop forked repository](https://i.stack.imgur.com/ztqaV.jpg)
Looking then on stackshare.io, we do not get much more material for a clear recommendation. If I had to choose a favourite, it is this one. Fork is again a tool which is good for handling many repositories and also provides a good intuitive way to explore the past and the current uncommitted changes.Finally Sublime Merge, Sourcetree and Github are neat, but very much focussed on single repository handling.SmartGit seemed to be a bit too rigid in the UI handling, but delivers good overviews and comparisons.Tower is the tool for managing many local repos as you can import all and group them, but if it is them exploring the history, for me at least it seems that other tools were a bit nicer.One tool (GitUp) shines with visualization - It displays the history better than any other tool, but the rest is basic.We have one tool(Gitkraken) that tries to be a bit more different and tries to integrate some more own features.It is difficult to recommend a best tool. I announced proudly that I would recommend a tool instead of just listing them up and say the usual it depends.
![github desktop forked repository github desktop forked repository](https://www.earthdatascience.org/images/earth-analytics/git-version-control/github-clone-repo.gif)
But then again, the same thing to others. It does a solid job in exploring the past and changes. GitUp is a tool that shines with this visualization. In 2005, I dropped out of my ClearCase project and in all subsequent projects I did - no matter if it was Subversion, TeamFoundation Server or Git, I was missing the ClearCaseExplorer. I had some experience with other tools as well, such as Visual SourceSafe, but ClearCase was the tool I was using for two years and I loved it.