![]() ![]() You’ll see the URL of the page change to /git-book-fizzbuzz.gitīok pp. Once GitHub finishes, it will redirect you to the newly-created fork under your personal GitHub account. Unfortunately, GitHub no longer shows the fork-in-a-book-on-a-copier image :[ You’ll see a progress screen indicating that GitHub is creating your fork: Now, click the Fork button at the top-right corner of the page: In a browser, open the following URL for the repository: There’s a bug in the code, so you’ll fix it then submit a pull request for your changes. For multiples of three, you print Fizz, for multiples of five, you print Buzz, and for multiples of both three and five, you print FizzBuzz.įor example, here are the first fifteen items: 1įor this tutorial, you’ll create a fork of a repository that implements FizzBuzz. In case you haven’t, it’s a programming task where, for numbers from 1 to 100, you print either the number itself or a word. Getting startedĪs a software developer, you’ve likely heard of FizzBuzz. You’ll also learn how to merge in open pull requests and branches from other forks. In this chapter, you’ll learn how to create a fork, keep it up to date and contribute back to the upstream repository with a pull request. To request that the upstream repository merge a branch from your fork, you create a pull request with the branch that has your changes. The original or source repository is conventionally referred to as the upstream repository. This personal, public copy of the project is called a fork. When you don’t have push access to a project, you’ll need to push your changes to a public copy of the project. It’s mainly used when contributing to open-source projects, but you can also use it with private repositories. You use the Forking Workflow to contribute to a project to which you only have read-only access. In this chapter, you’ll learn all about the Forking Workflow. 7.2 Working with the three flavors of reset.6.8 Challenge: Remove IGNORE_ME from the repository.6.7 Using filter-branch to rewrite history.5.9 Challenge 2: Rebase your changes onto main.4.8 Challenge: Rebase on top of another branch.4.3 Creating your first rebase operation.3.6 Challenge: Clean up the remaining stash. ![]() 2.8 Challenge: Resolve another merge conflict.1.3 The Git object repository structure.Section I: Advanced Git Section 1: 7 chapters Show chapters Hide chapters ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |