![]() It’s interesting to understand how GitHub built a cross-platform application like this. Or you could simply use GitHub Desktop to monitor the Git tooling built into your IDE. ![]() As the client is connected to the cloud service, it keeps up to date with changes in all the branches, showing where pull requests have been made and where commits in the master branch haven’t yet been merged into your current branch.Ĭommits and pull requests are handled just like you're used to with GitHub, with file system integration so that you can use your choice of editors and development tools. A drop-down menu lets you pick a branch, with the graph showing the commits since you last branched off. Looking rather like a public transport map, it gives you a view of your current branch and the commits you’ve made. The tutorial is built into the app and can be hidden at any time.Īt the heart of the tool is a graphical view of a repository, showing the branches and differences, that helps you navigate through your and your collaborators' changes. Once installed it walks you through a quick tutorial showing you how to branch a repository, commit changes, then handle pull requests and merges. It handles synchronizing your code with the cloud, managing branches, and showing changes - so you can work in your usual code editors without having to worry about whether it has integration plug-ins.Īcquiring GitHub Desktop is quick and easy, with the installer downloading the latest version as part of the install process. With both Mac and Windows versions, built using a common core, it’s an important tool. ![]() GitHub Desktop is intended to simplify working with the service, bringing common GitFlow techniques to your desktop while still giving you an offline copy of your repositories so that you can work anywhere. Git’s cloud incarnation, GitHub, has become the public face of source control - where recruiters look at candidates’ code and commits and where much of the world’s open source software is developed and shared. From its birth of scratching Linus Torvalds’ version-control itch, it has grown to become the repository of choice. Since returning, I've spent more time fiddling with this desktop app and command line than I have actually doing any work.Git has become the lingua franca of code. I was able to create, clone, or modify (including the files) any repo from the app itself. It's been some time since I've been active on GitHub and I remember an app they had released a few years ago, perhaps just an earlier edition of this, that was far easier to use and actually worked. Never mind the contradictory and often confusing information that is available for the app. I experienced the same issues going through the tutorial, waiting nearly two full minutes to "commit" the ReadMe it auto-generated. What the hell is the point in having a desktop app if I'm still forced to use command line because the app is so awful? Cloning five files took me ~20 minutes. I actually had to take the longer route and use Git Bash. One of my repos is a 10k file package that totals less than 30MB and yet, when adding the repo via GitHub Desktop and trying to do my first commit to master (before publishing), it just sits for hours. ![]() It's slow, awkward, and frequently crashes. I'm still relatively new to GitHub but already hate this current version of GitHub Desktop.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |