![]() The local master branch also tracks the remote repository, so that git fetch, git pull, and git push automatically apply to origin when run with master checked out. Your remote cloned repository is given the special name origin by your local clone repository. Nothing to commit (working directory clean) $ git clone private, local clone automatically has a master branch that matches the master branch of your public, remote repository. If you clone the read-only version, then you won’t be able to push changes back to the public repository. ![]() Actually, there are multiple URLs, but you’ll want to make sure the clone the SSH version, which is read-write. The URL of my public repository is listed on. Thus, I have to clone the repository on my own local Mac. Besides, I wouldn’t be able to run Xcode anyway. The catch is that I can’t work directly on my public repository, because I don’t have shell access to GitHub’s servers where the repository resides. The fork is my public repository, which GitHub users can pull from. When I clicked that button, it created a fork of the project at. If you haven’t already forked ClickToFlash, you’ll see a “Fork” button on. Other GitHub repositories such as my own and Simone Manganelli’s are forked from Rentzsch’s. (I suspect Holtzman, Holtzmann, or Holzmann.) Fortunately, several developers including ‘Wolf’ Rentzsch preserved the source code, and Rentzsch’s GitHub repository has become ‘official’. We still don’t know the identity of ClickToFlash’s author. Not long thereafter, the project disappeared without a trace. The project first appeared on Google Code, posted by an anonymous donor. Mystery surrounds the origin of ClickToFlash. I’ve chosen ClickToFlash as my example, because people are familiar with it, and I’ve contributed code to the project. My explanation will give you the steps of the GitHub workflow using an example project. The most confusing aspect of working with GitHub, in my opinion, is repository management, and that’s what I’ll explain here. I won’t discuss the process of installing Git or signing up for GitHub account you can find documentation for those elsewhere. While GitHub does make social coding convenient, there is still a significant learning curve. After you make changes to your GitHub repository, you can send pull requests to other GitHub users to notify them of the changes, and they can pull your changes into their own repositories. If you want to work on a GitHub project, you simply fork the project’s GitHub repository, creating a new GitHub repository in your name. It allows anyone in the world to collaborate on any GitHub project without having to worry about repository commit privileges or patch files. GitHub is a web site that hosts public Git repositories. “It”, in this case, is Git, or more specifically, GitHub. This blog post is intended to be a reference not only for you but for me, because I always forget how it works.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |