How to send pull request on Git

We have recently migrated to Git from SVN. We have setup a bare repository on one machine in our LAN network and cloned on other machines. Now when anyone do the changes and commits we want that he sends the pull request 开发者_运维技巧to the bare repo (by telling or emailing or any other way) after that one will go through the changes and pull it on bare repository (same as it works on GitHub).

Do we need to install any interface or there is some commands in Git itself?

Both Git (the software) and GitHub (the web service) have a concept called "pull request", and unfortunately they are not exactly the same thing.

Native Git

The native Git request-pull command has a very short manual page with the following one-sentence description:

Summarizes the changes between two commits to the standard output, and includes the given URL in the generated summary.

This is a fairly low-level command that generates a short summary of changes that is suitable for posting to a mailing list. Other users can use the URL published in this "pull request" to manually pull changes into their own repository.

GitHub Pull Requests

When using the GitHub web service, a Pull Request is a full-featured interactive collaboration tool. A GitHub pull request has:

• a more detailed description of the changes than just the individual commit summaries
• notifications automatically sent to users who have chosen to watch the project
• an online review interface where others can comment on proposed changes
• discussion comments for recording conversations about commits
• central management of pull requests so they won't get lost

It is worth noting that Linus has his own opinion on the relative utility of these two features.

Conclusion

The two "pull request" features described above are similar in spirit but completely different in implementation. In particular, the git request-pull command cannot be used to create a new Pull Request on GitHub. You have several choices if you want to support "pull request" type functionality:

• Use GitHub. This definitely involves the least effort, but if your project is not public you'll have to pay GitHub to host a private repository. Some people might not be comfortable with this choice.
• Use Gerrit. Gerrit is an open-source server program you can download that provides many features similar to those available in GitHub. It is especially well suited to collaborative code reviews.
• Use git request-pull and a mailing list. Using this method requires a lot more discipline from your engineers, as it's easy to misplace or mishandle mailing list messages. There is no central accountability associated with this method.

The term "pull request" is not a github specific term.

There is a git request-pull command, you can read more about it here: http://linux.die.net/man/1/git-request-pull

For some more in depth explanations and save you some googling look at:

• http://git-blame.blogspot.com.ar/2012/01/using-signed-tag-in-pull-requests.html
• http://wiki.koha-community.org/wiki/Sending_a_%22request_to_pull%22

This is not a new feature BTW.

EDIT: This alternative answer was made before the originally accepted answer by @Greg Hewgill was rewritten. I posted it because this is the answer I was looking for, and I think it suited the question which asked about doing pull requests for users not necesarilly using github (Yes, not everyone using git uses github, at least not all the time). Now that the orignal answer was rewritten making this difference explicit I'll leave this answer the way I originally posted it just for the record.

The "git way" of doing this would be that all the developers have their own public bare repository (read acces to all, write acces for the developer himself) on the server as their "origin". And if you like an additional "trunk" (or "stable" or whatever you want to call it) bare repo that some or all developers have write access to. The developers mirror their repo on their public repo, and pull from the other developers. That way you don't have to worry if you push something to your public repo that doesn't work yet. (The developers can just pull from you to a test branch and see if it works.) When you have a stable canonical branch you can push it to the "trunk" repo.