Bitbucket Pull Requests - The Branch Way

Рет қаралды 91,958

Күн бұрын

In this video, we look at creating pull requests on Bitbucket. The traditional way of forking PRs is presented, but we favor the branching technique more. We'll see how to create a branch with out changes, push that branch to the main project repository, and create a pull request using that branch.
Link to webpage: www.srcmake.co...
Twitter: / srcmake
Twitch: / srcmake
Discord: / discord

Пікірлер: 61

@seangates7988 4 жыл бұрын

Very useful video. I'm fairly new to Git. I thought it was interesting how you made the changes in 'master' then created the branch for the pull request. However, I used this technique serially for two separate pull requests for two different files in master (so two new branches back-to-back off master) and had some difficulty afterwards getting my local master and origin/master synched up, even after merging the pull requests with origin/master. Eventually I had to “git reset --hard origin/master” to get things corrected. Your steps perhaps assume a new clone between pull requests (?) but henceforth, I’ll definitely “git checkout -b foo/bar” from master before making and pushing any changes.

@st0nedeft 2 жыл бұрын

Thanks man! I should have watched this video first before wasting countless hours trying to figure pull requests LOL

@Carlos1979Mad 4 ай бұрын

Useful staff. Muchas gracias Sir

@diegobm23 2 жыл бұрын

Thanks man, I wanna start using pull requests in my team and this was really helpful.

@RoyalTutorial 5 жыл бұрын

Very clear man. Best explanation I have viewed so far!

@HiltonFernandes 2 жыл бұрын

Great explanation. I'm new to Bitbucket, and your video is a nice welcome message.

@sretepmf Жыл бұрын

Very succinct and clearly presented. Thank you.

@johnbrewer7221 2 жыл бұрын

Thanks for this! When I ask here at work I literally get a different answer and a different workflow every time. The workflows never work right and we wind up having to figure it out as we go. Basically wind up with a detached workflow and nothing is learned.

@MO3rOBOuBbICEP 5 ай бұрын

Big thanks!

@stillchris4171 3 жыл бұрын

Nice pace and delivery! Keep it up dude.

@Churriittoo 2 жыл бұрын

Thank you, man

@MightyMike55 5 жыл бұрын

Great Video srcmake. Your content delivery is on point, keep them coming *subscribed*

@vishnupradhaban2189 Жыл бұрын

great content!!

@guitarDad100 5 жыл бұрын

Great lesson. Very helpful. Thanks for posting.

@swarnashissarkar4767 2 жыл бұрын

Very well explained Thanks!!!

@rajneeshraikwar6285 2 жыл бұрын

Thank You Sir , Really this video help me lot

@BieelsZaitsev 4 жыл бұрын

dude, you helped me a lot

@ShyamKumar-rl3rw 2 жыл бұрын

Nice, thank you. Can u please make video on how to create webhook to integrate bitbucket master branch ( after final changes ) to Teamcity . Thank you

@funzoned9008 2 жыл бұрын

Thanks, this video was useful! 😄

@seshagirik4066 3 жыл бұрын

Thank you!

@akhilthakur251 4 жыл бұрын

Thank bro nice video. also, create a video on how to work with diverged branch.

@RajatSingh-lv5op 4 жыл бұрын

you are the G bro

@jaysonbrenton6400 4 жыл бұрын

Thanks mate. Good info!

@ankitchanpuria7176 4 жыл бұрын

Nice Video, thanks a lot !

@palomabalbiano7392 3 жыл бұрын

muchas gracias amigo, me ayudo mucho

@JonatanEdOrtiz 3 жыл бұрын

Thanks

@bcoder1566 4 жыл бұрын

Nice video, really helped

@thefonsotube 4 жыл бұрын

"The Branching way": Do all team members have ability to Merge on the master using the Branching way?

@srcmake 4 жыл бұрын

Hi UncleFonso. It depends. If your repository is private then the person who added you might have specified what kind of permissions you have (read, write, admin) which affects your ability to merge into master. Not only that, but the repo might have rules like "a PR must have 2 approvals before being able to be merged". So you should check what kind of permissions you have and how the repository is set up if you're running into any merge issues.

@danielbaena4691 4 жыл бұрын

Thank you bro

@smaug9833 2 жыл бұрын

What privilege do we need to push the new branch feature/... into the remote repo?

@satyajeetrathour3721 4 жыл бұрын

awesome , ring pressed.

@inbasivahappy6727 4 жыл бұрын

Can i know how to create dummy project for uploading our team projects on it.. Please help me.

@chiranjeevimanchala7965 3 жыл бұрын

Get email from bitbucket devops when merge happens as a notification

@EverydayRoadster 4 жыл бұрын

The video stops at a state where your local repo is still in a branch.

@DeepakVerma-ol2oe 2 жыл бұрын

wonderful

@oatmealduck7937 3 жыл бұрын

good stuff

@dillipkumarsahu 5 жыл бұрын

This is not working in all scenarios. its adding some other changes also. Could you please improve this ???

@balazsio 3 жыл бұрын

Thanks the video. Funny fact:Dolphins are mammals, not fish.

@ruslanfilistovich9467 5 жыл бұрын

Спасибо!

@TheAnimeist 3 жыл бұрын

Filleted and grilled is the best fish.

@Farmani 5 жыл бұрын

any reason why you didn't create the branch first and then make your commits?

@srcmake 5 жыл бұрын

There's no reason in particular; you're free to do either one first. Branch -> add -> commit -> push OR add -> commit -> branch -> push. It ends up being the same thing.

@Farmani 5 жыл бұрын

srcmake cool thanks. And what if we want to make sure that master is up to date before we make a pull request?

@srcmake 5 жыл бұрын

You can look at the original branch (which I'll call master in this post, but may not necessarily be the "master" branch in all cases) on the bitbucket website itself, and if your branch is a bit behind (meaning there were changes to master during the time you were making your own code changes (Ex. You download master -> you make code changes on your computer -> I update master and push the changes to bitbucket-> you try to make the PR -> your PR branch doesn't have the changes I made)) then bitbucket has an easy way on their website to merge those changes on master onto your branch. (They call it syncing.) However, you should generally keep your branch/PR the same as long as it works for you, because there are potentially merge conflicts if you try to update your branch with changes that happened on master. TL;DR keep your branch the same as when you downloaded it, unless a change happened on master that you want on your branch specifically to help you test/expand your code.

@Farmani 5 жыл бұрын

@@srcmake Thanks, do you think it would be a good idea to run git pull origin master after we've cloned the master repo before we make a pull request?

@srcmake 5 жыл бұрын

@@Farmani Don't.