Topic: How to create a PULL request (Read 90811 times)

To create a pull request, you must have changes committed to the your new branch. Go to the repository page on github. And click on "Pull Request" button in the repo header. Pick the branch you wish to have merged using the "Head branch" dropdown.

There is a beautiful tutorial posted by github ,I think its a video and a step by step tutorial on one of the GH pages .That is the most simplest tutorial I have seen yet.

Since the project is open source, anyone can change the files.  However, this creates a "fork", their version of the software is different from everyone else's.  This means that they need to incorporate any future changes into their fork.

A pull request allows them to submit the change back to the main project.  If it is accepted, the changes become part of the official version of the software.

You have explained the method and its use that well even someone who not really was into coding could understand the wisdom in the method. Thank you for this information! It also is a nice example when PULL request becomes useful.

Great, thanks for the info.

I stand by. Thanks!

pull requests are a mechanism for a developer to notify team members that they have completed a feature. Once their feature branch is ready, the developer files a pull request via their Bitbucket account. This lets everybody involved know that they need to review the code and merge it into the master branch.

But, the pull request is more than just a notification—it’s a dedicated forum for discussing the proposed feature. If there are any problems with the changes, teammates can post feedback in the pull request and even tweak the feature by pushing follow-up commits. All of this activity is tracked directly inside of the pull request.

Git Workflows: Activity inside a pull request
Compared to other collaboration models, this formal solution for sharing commits makes for a much more streamlined workflow. SVN and Git can both automatically send notification emails with a simple script; however, when it comes to discussing changes, developers typically have to rely on email threads. This can become haphazard, especially when follow-up commits are involved. Pull requests put all of this functionality into a friendly web interface right next to your Bitbucket repositories.

Anatomy of a Pull Request
When you file a pull request, all you’re doing is requesting that another developer (e.g., the project maintainer) pulls a branch from your repository into their repository. This means that you need to provide 4 pieces of information to file a pull request: the source repository, the source branch, the destination repository, and the destination branch.

Git Workflows: Pull Requests
Many of these values will be set to a sensible default by Bitbucket. However, depending on your collaboration workflow, your team may need to specify different values. The above diagram shows a pull request that asks to merge a feature branch into the official master branch, but there are many other ways to use pull requests.

How it works

Pull requests can be used in conjunction with the Feature Branch Workflow, the Gitflow Workflow, or the Forking Workflow. But a pull request requires either two distinct branches or two distinct repositories, so they will not work with the Centralized Workflow. Using pull requests with each of these workflows is slightly different, but the general process is as follows:

A developer creates the feature in a dedicated branch in their local repo.
The developer pushes the branch to a public Bitbucket repository.
The developer files a pull request via Bitbucket.
The rest of the team reviews the code, discusses it, and alters it.
The project maintainer merges the feature into the official repository and closes the pull request.
The rest of this section describes how pull requests can be leveraged against different collaboration workflows.




you can check in
https://www.atlassian.com/git/tutorials/making-a-pull-request/how-it-works

its not working for me

will done

This is the right method for creating pull request im using this in my every project. If you have any query then contact me via email [email protected] or +13479604186

Im not clear with the pull request and github.. Can anyone say me clearly about this.. Thanks

Thank you for the post and information. 

Pull requests let u tell others about changes you have pushed to a repository on GitHub. Once a pull request is sent, interested parties can review the set of changes, discuss potential modifications, and even push follow-up commits if necessary.

A good start:
https://help.github.com/articles/set-up-git/

if you get stuck, lots of people will be able to help.  ;-)

In simple Words, Pull requests let you tell others about changes you've pushed to a GitHub repository. Once a pull request is sent, interested parties can review the set of changes, discuss potential modifications, and even push follow-up commits if necessary.

Example:
Imagine that you built your work on your master branch on top of the v1.0 release, and want it to be integrated to the project. First you push that change to your public repository for others to see:

git push https://git.ko.xz/project master
Then, you run this command:

git request-pull v1.0 https://git.ko.xz/project master
which will produce a request to the upstream, summarizing the changes between the v1.0 release and your master, to pull it from your public repository.

If you pushed your change to a branch whose name is different from the one you have locally, e.g.

git push https://git.ko.xz/project master:for-linus
then you can ask that to be pulled with

git request-pull v1.0 https://git.ko.xz/project master:for-linus

Do I need to create a pull request to suggest translation fixes?

Thanks for this OP, This is something I have been interested in learning, I have been using git for a few months, but only within my own repo, so I have been avoiding learning how to do this.
btw @zulu I love using the -m flag as well, 

it is used to request a merge of different versions of versioned files in so called "Versioning file systems"
just google for the term

what if i pull 2 requests

Yep.  Finally figured it out about a day after I made that post.  Thanks though.

I've been getting used to Git, but it's a very annoying RCS.