CODEWITHSUNDEEP
github
Sunshine
Sunshine

Reputation: 489

GitHub - how to submit individual pull request in case of multiple commits

I've made multiple commits to my local repository and now I intend to do pull request to submit these changes over to the source/master.

When I do a pull request, it automatically includes all of my commits. I couldn't locate a way to submit each commit in its own pull request. Could someone please give some pointer on how to do this on GitHub.

Update To clarify on this question, I forked a new local repo from upstream/master. Then, in my noobie-ness, I made new files in my local master itself without branching repo out first. So, effectively, my question is with these changes committed to local master repo, is there a way to raise pull requests for each new file one by one, and not for all of them in one go.

Many Thanks.

Upvotes: 16

Views: 8152

Answers (2)

Joakim Nohlgård
Joakim Nohlgård

Reputation: 1852

I'm not sure if there is a better way in GitHub, but in general, you can create a new branch for each pull request, cherry-picking the commits you want for each request. The new branches should preferably be based on upstream master to make the merge painless.

Using command line git, using origin as your own github remote repo, upstream is the upstream remote:

git checkout -b {my_pull_request_feature_branch} upstream/master
git cherry-pick {sha1_of_first_commit_for_feature_X} [sha1_of_another_commit_for_feature_X] ...
git push origin {my_pull_request_feature_branch}

Repeat for each pull request.

When you do a pull request on GitHub you can then choose which branch you want to send in your request.

Upvotes: 21

poke
poke

Reputation: 388393

A commit does not stand on its own, it always links to the full previous history. So if you ask to pull commit B which depends on your commit A, then you are also asking to pull A, because your work in B depends on it.

If you want to submit multiple independent pull requests, you should make sure that those commits are completely independent of each other. So they should be on their own branches. This also makes it easier for the project maintainers to integrate your pull request, as they can just merge the branch without having to cherry-pick stuff.

Upvotes: 6

Related Questions