# Git question: multiple PRs

**URL:** https://discourse.julialang.org/t/git-question-multiple-prs/2695
**Category:** Internals & Design
**Tags:** question
**Created:** [March 16, 2017, 11:37am UTC](https://discourse.julialang.org/t/git-question-multiple-prs/2695 "2017-03-16T11:37:39Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [March 16, 2017, 11:37am UTC](https://discourse.julialang.org/t/git-question-multiple-prs/2695/1 "2017-03-16T11:37:40Z")

</div>

This is more of a git question, but since I found many possible solutions online I am wondering if there is a preferred way to do this in the Julia package ecosystem.

Consider a git repo for a package, for which I want to submit multiple PRs (bug fixes, new features, etc) simultaneously (in practice, simultaneity happens because merging PRs takes time).

So I create a new branch from `master`, named `pr1`, write the code, and submit a pull request. Now for the second PR `pr2`, should I branch from `master` or `pr1`, as in

```julia
master -> pr1 -> pr2

```

? Or branch parallel, eg

```julia
master --+--> pr1
         |
         +--> pr2

```

If I branch from `master`, but merging takes time and I want to use the fixes myself locally in the meantime, what’s the best way to do it? Should I create a third local branch, and merge `pr1` and `pr2` into it?

---

<div class="post-metadata">

### Author: ![tkelman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkelman/32/692_2.png) [@tkelman](https://discourse.julialang.org/u/tkelman)
#### Post date: [March 16, 2017, 11:42am UTC](https://discourse.julialang.org/t/git-question-multiple-prs/2695/2 "2017-03-16T11:42:29Z")

</div>

I’d usually say to do two separate branches each starting from master, especially if the changes are mostly independent.

A local branch with both changes cherry-picked or merged sounds good for using it locally - you could also have the changes applied as diffs to your local copy without necessarily committing them. Would just need to remember to check back out a proper branch or release when everything gets incorporated upstream.

---

<div class="post-metadata">

### Author: ![innerlee](https://avatars.discourse-cdn.com/v4/letter/i/b19c9b/32.png) [@innerlee](https://discourse.julialang.org/u/innerlee)
#### Post date: [March 16, 2017, 3:34pm UTC](https://discourse.julialang.org/t/git-question-multiple-prs/2695/3 "2017-03-16T15:34:35Z")

</div>

I always create lots of `deploy/pr1_pr2_pr5`-like branches for specific functions/fixes I want to use.
