How to make a pull request on an open source project

I'm just walking you through how you could use git to fork an upstream branch, make a new branch, add changes to your git stage, commit your changes, and then push those changes to your branch, make a pull request (PR) to the upstream github repo, and then also how to update your master branch to match the upstream branch by using git fetch and git reset --hard.
🔔 Newsletter eepurl.com/hnderP
🤓 ES6 Udemy Course tinyurl.com/yxdvf2zl
🐦 Twitter / thewebdevjunkie
📷 Instagram / thewebdevjunkie
💬 Discord / discord
📁. GitHub github.com/codyseibert/youtube

[@BenRogersWPG]

I've been a developer for 15 years. Been on GitHub for 10 years, however I have never done a pull request. I'm doing some Arduino development for a hobby and wanted to contribute to a project I care about. This guide helped me, and gave me all the info I need to confidently contribute to the repo. I am happy to report, I just completed my first pull request because of this video. Thanks so much for the great and helpful video!

[@codewithlenny]

Same thing here! I've never created a pr despite being on GitHub for 5+ years. I am currently working on a robot with some colleagues and pull requests have been all the buzz around here. Time to get back to the basics ;)

[@JohnnieWalkerGreen]

#METOO I came here because of a "pull request." Wish me luck for not screwing anything.

[@Mikesco3]

Same here

[@Mikesco3]

Just completed my first pull request to a project that helped me a lot... The pull request got confirmed too!!! This video was fantastic in helping do that...

[@JohnnieWalkerGreen]

@@Mikesco3 Hear hear...

[@GennadyPodrezov]

Such a great tutorial dude. Very concise, straight to the point yet easy to understand. Impressive job man. I wish all people who are really good at something had the ability to explain it as effective as you do!

[@Mikesco3]

Great video... I'm so glad you went into the nuance regarding pull requests, a lot of other videos only say what to do, but fail to provide the logic behind it...

[@nitika1111]

You've made this real simple! Made note of steps and feeling ready for my first open source contribution. Thanks!

[@WebDevCody]

Happy coding! Glad you feel comfortable with git a bit more!

[@kerokeromeow]

Thank you so much for this! It was really easy to follow you and finally made my first PR :)

[@DSCS_ShilpiPrasad]

Thanks loads!! U really saved me! I've been trying to create a PR for almost about 2hrs when I finally came across this video.

[@msstarcheetah]

I was stuck and this came in clutch to clear up my uncertainties, thanks so much!

[@jantack7186]

Very helpful. Clearly structured in terms of content. The sound quality is very good and the pronunciation is clear. Especially for non-native speakers like me, this makes it easier to follow.

[@Mikesco3]

Just completed my first pull request to a project that helped me a lot... The pull request got confirmed too!!! This video was fantastic in helping do that...

[@jathebest2835]

This was very helpful and comprehensive for beginners like me. Your explanation is top-notch and I appreciate your effort to film the video. I'll revisit the video when I need to do a group project.

[@sharabhmishra8754]

Thank you so much bro. I made my first contribution today because of you. Now just waiting for approval

[@WebDevCody]

Let’s go!

[@lordcoco_]

super clear and helpful! appreciate the demonstration 🙏🏻

[@jonholdsworth7351]

Very good. Crystal clear and detailed.

[@mustafaaal-sahek8055]

thanks man, you made it very simple and easy to follow 🔥

[@vnoommuy]

Saved for later. Commenting to help with the youtube algorithm. Thank you for your videos and the work you put into them.

[@WebDevCody]

Thanks I appreciate that!

[@kevon217]

Very helpful walkthrough, thanks!

[@LeCyProductions]

So well explained, thank you so much.

[@sepehrsarjami]

Thanks, your video helped me a lot! Very well explained and detailed.👍

[@PravinKumar-mc8tz]

Thanks Brother Your Help was Appreciated

[@rajkishan3690]

Thank you Cody ,it was helpful.

[@prazeet7246]

Great content, Perfectly explained!

[@christopheramoisan]

Thank you I look forward to my first PR

[@walidzao]

Thanks for the video, straight to the point and informative !

[@yuchen3587]

Absolutely practical and clear!

[@sarveshworld]

Finally done my first PR... Thanks

[@oluwaseunajibowo7422]

Thank you, this is just too precise 🙌

[@Creativeviiibes]

You are a life saver for me ,found this best video of yours at the right time 🙂...

[@jwdmsd]

One additional step (that I think you missed) would be to fetch+merge the latest master from upstream into your branch (testing-demo) right before creating a pull request. This is crucial in case there are other commits made to the upstream master while you're working on your branch.

[@WebDevCody]

Git pull does a fetch and then a merge automatically

[@Sky-yy]

Aye whatta conincidence,I was asked to pull a repo at job,using vs code or gitbash. This what I was looking for but I already watched it somewhere else. But my favorite KZbinr uploaded so gonna be watching again.

[@WebDevCody]

Hope it helped!

[@user-mv2yg4mm3m]

Excellent tutorial, very helpful :)

[@Sky-yy]

Just completed this one, amazing one 👌

[@WebDevCody]

Good! Thanks for watching!

[@sheldonfourie5959]

This is really helpful seriously!

[@KnifeChampion]

Very informative and concise vid thank you

[@alpachino468]

I've been using Git for many years but I'm still a bit apprehensive forking an open-source project, adding my changes, and then opening a PR, for fear that the repository owner might be a jerk and make me look foolish. Totally understand my fear is irrational, and it's always good contributing to projects, so I hope my insecurities don't put anyone else off... 😊

[@mohamedaminesaadani1975]

thanks a lot mate! It make it simple for me.

[@erpadminpspl7868]

thanks for this it is very helful because this type of video is very less on youtube.

[@suyash.01]

very well explained!!

[@nested9301]

wow this video is so helpful !

[@user-po9dy4tx9o]

This is gold, thank you

[@hardikchavada8974]

nicely explained 👍

[@ogo_zita]

You are a life saver.

[@darshantank554]

Beneficial video Thanks :)

[@monicaluo8983]

Love this video!

[@MrCryoJack]

This is good Wanted to know as I am starting to learn git

[@vijay-00700]

Thank you so much

[@rubaadel8576]

Thank you very much

[@user-jb5zi9ne7m]

Thank You!!

[@SeibertSwirl]

Good job babe!!

[@vihaanthora8089]

Thanks for the video, it was really helpful :) I had a question for you, after the maintainer merges the pull request into the master branch, should we go ahead and delete the branch from our forked repo?

[@WebDevCody]

you can if you want to just keep your fork "clean". We usually delete all old branches after they get merged to master / main.

[@vihaanthora8089]

@@WebDevCody Thank you, that helps :D

[@peuchex7318]

Amazing tutorial! Got to create my first PR and open source contribution thanks to you! One small question tho, what if a PR "A" hasn't been merged into the upstream repo yet and you continue to work on a another PR "B" but you need the changes from the PR "A" to move on? Thanks in advance!

[@WebDevCody]

You can merge branch A into your branch B and then you’d just have a single PR with the combined code

[@internetandcomputerprobe4426]

informative brother

[@Rs-nh7zx]

Loved this!! Just wondering after adding upstream, can we do git pull upstream to get all the changes from the upstream master?

[@WebDevCody]

I think so. If you’re current on the master branch I think you can do ‘git pull upstream/master’ to grab the latest changes from upstream master and merge them into your branch. Although, I’m not 100% certain

[@ahmedayachi5889]

hello, why git reset --hard upstream/master not git pull upstream master ?

[@haseebsheikh6101]

Helpful

[@nivethanyogarajah1493]

Nice!

[@CaliburPANDAs]

if you do "git push upstream master", are you bypassing the PR and merging directly?

[@WebDevCody]

I think so yes

[@hilalsemercioglu8599]

a quick question. I'm contributing an open-source project. But my new pr shows the previous changes even if the owner approved & merged my pr. What should I do for preventing this?

[@WebDevCody]

I'm not sure what you mean by previous changes

[@jineshjain4722]

Best Video

[@bistabishwo]

Thank you so much, this is really helpful. But when I tried " git push origin local-branch" it says permission denied. Does this has to do with what the permissions specified on original repo?

[@WebDevCody]

You can only push to your fork if you’re not a collab on the repo

[@bistabishwo]

@@WebDevCody I got it, I forked the repo and cloned it from the original repo instead from my forked repo.

[@yuchen3587]

I am a bit confused. When I am developing something on my testing branch and there is an update in the upstream repo, I should pull the update into my master branch. But after the pulling, my testing branch is still not updated. Should I then merge my master branch into my testing branch?

[@WebDevCody]

yes, you'll need to merge master into your testing branch. You might be able to do `git pull master` should work I think or `git pull upstream master`

[@yuchen3587]

@@WebDevCody Cool thank you for your quick reply!

[@sashaikevich]

Nice theme. What’s it called?

[@fancyAlex1993]

Couldn't you do git fetch and git merge / git pull after setting upstream instead of git reset ?

[@WebDevCody]

Yes I think so. I don’t remember what I taught in this video, but you should just be able to do a git pull upstream main to get the latest changes. Rebase also works

[@thewayfarerseye]

Clarification - you have forked and made your changes to a feature branch locally and then pushed to your remote forked repo. Do you think if this was merged to your master and then a PR is raised to the open source repo, would that be the ideal way to avoid the git reset master branch at later point? Or is it done because you want to wait and see the repo owner to validate and only when it is merged with master, you want to merge the same to your forked repo master branch.!

[@MohddAlii]

Do we have to wear a backpack for making a pr?

[@WebDevCody]

Yes highly recommend

[@nick-pu4zae]

👌

[@avinashmurmu9070]

after 11:10 I couldn't understand, too difficult. I understood the problem but why are we writing those commands and what are the different possibilities. Maybe I need to watch some more videos.

[@Johnny-rn8fb]

noice

[@DadundddaD]

So much words, so fast speaking, but you could really compress all the info, for people for whom it's the first pull request

[@christopheramoisan]

Thank you I look forward to my first PR