{"id":4206,"date":"2018-03-21T11:02:22","date_gmt":"2018-03-21T06:02:22","guid":{"rendered":"https:\/\/thedevcouple.com\/?p=4206"},"modified":"2018-03-27T17:57:51","modified_gmt":"2018-03-27T12:57:51","slug":"how-to-create-a-pull-request-on-github","status":"publish","type":"post","link":"https:\/\/thedevcouple.com\/how-to-create-a-pull-request-on-github\/","title":{"rendered":"How to Create A Pull Request on GitHub?"},"content":{"rendered":"

Pull requests are the way of contributing <\/strong>or collaborating<\/strong> on a project on GitHub. Let’s say you want to contribute to a repository on GitHub, maybe fix a bug<\/strong> or a typo<\/strong>. Since you don’t own the repository, you can’t directly make the changes<\/strong>. So, what you do is, you simply make a copy\/fork<\/strong>\u00a0of the repository, make changes<\/strong>, and create a pull request<\/strong>.<\/p>\n

\n

\"create<\/a><\/p>\n<\/div>\n

When you create a pull request, the owner of the original repository is notified that you have created a pull request and proposed some changes. The repository owner can review<\/strong> the changes, merge<\/strong> them, ask for a revision<\/strong>, or even discard<\/strong> them. This is how pull requests work on GitHub.<\/p>\n

\n

\ud83d\udd25\u00a0FUN FACT<\/strong><\/p>\n

Ever wondered why it is called pull request, not push request? The reason is that you ask the repository owner to pull changes from your copy<\/strong>.<\/p>\n<\/div><\/div>\n

\u26a1\u00a0Steps to Create A Pull Request<\/h2>\n

According to our understanding of how pull request works, there are three<\/strong> basic steps to create a pull request:<\/p>\n

    \n
  1. \ud83c\udf97 Fork the repository<\/li>\n
  2. \ud83c\udfac Make changes in copy<\/li>\n
  3. \ud83c\udfaf\u00a0Create a pull request<\/li>\n<\/ol>\n

    \u2192 Fork the Repository<\/h3>\n

    To fork a repository, open the repository and click on the Fork button<\/strong> at the top left corner. For example, I am forking this<\/a>\u00a0Hacktoberfest repository by Ahmad Awais<\/a>.<\/p>\n

    \"Forking<\/a><\/div>\n

    \u2192 Make Changes in the Copy<\/h3>\n

    Next step is to make the changes in the copy i.e fix the typo,<\/strong> bug<\/strong>, or whatever you want to contribute. You can either do it directly on GitHub \u2013 I will be doing in this guide \u2013 or you can clone the repo and push changes from your machine.<\/p>\n

    At the time of writing this piece, I just noticed that there’s a colon missing in front of a heading in this repo. So, I am going to propose a fix for it.<\/p>\n

    \"Making<\/a><\/div>\n

    Since it’s a minor fix, I can simply go ahead and edit the file on GitHub. However,\u00a0I do not\u00a0<\/strong>suggest<\/strong> to edit files on GitHub for major changes in the repo. To do so, open the file in your copy of the repo and click on the\u00a0Edit\u00a0<\/strong>button<\/strong> at top right corner.<\/p>\n

    \"Editing<\/a><\/div>\n

    Clicking on the icon will open the file for editing. Make the changes you want to do and scroll down the screen. At the bottom, you’ll see a section named\u00a0Commit changes<\/strong>. In this section, you provide the description and title of the proposed changes. Fill in the details and click on\u00a0Commit Changes<\/strong> button.<\/p>\n

    \"Adding<\/a><\/div>\n

    Once you have clicked the Commit changes button, your changes will be saved in the file. Now, your copy of the repo is different from the original repository and you can create a pull request.<\/p>\n

    \n

    \u26a1 Tips on Writing a Good Git Message by Ahmad Awais<\/a><\/strong><\/p>\n