Github desktop fork repo3/31/2024 You obviously can’t work directly on the main project files, so you first need to take a copy of them to your own GitHub account. Note that each of the steps will get their own articles in the future as parts of this series. Boxes are shown in blue when they are synchronised with the current official repo red means they have got out of sync green is used when the upstream repo has been changed. The diagram above will be used throughout this tutorial to illustrate the various exchanges. It is important to understand the interaction between the three players at all stages in this process. The objective of this tutorial is to show you how, using the GitHub Desktop, to contribute to an open source project by working on files from some remote repository and then submit them (make a pull request) so they can be merged into the “official” project. Local – the files on your local machine where you will be making your changes. Origin – your fork of the project files that live in your GitHub account, and.Upstream – the “official” project files that live on the main repo in GitHub,.The repo also stores each file’s revision history. Files get stored in a repository (repo for short) which is like a separate locker for each project. You could think of it as the umpire in a sort of complicated game of tennis involving three players, except they will be bouncing around files instead of tennis balls. GitHub Desktop is a graphical tool that helps you to use GitHub without having to deal with the command line (which, let’s face it, does tend to discourage a lot of people). This is the introductory part of a series of tutorials on GitHub Desktop. An introductory guide to the GitHub Desktop
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |