# Making a Pull Request to PyFR on GitHub

**URL:** <https://pyfr.discourse.group/t/making-a-pull-request-to-pyfr-on-github/297>\
**Category:** Just Starting\
**Created:** [22 September 2020 15:21 UTC](https://pyfr.discourse.group/t/making-a-pull-request-to-pyfr-on-github/297 "2020-09-22T15:21:43Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gavin\_Wiggins](https://avatars.discourse-cdn.com/v4/letter/g/cdc98d/32.png) [@Gavin\_Wiggins](https://pyfr.discourse.group/u/Gavin_Wiggins)\
**Post date:** [22 September 2020 15:21 UTC](https://pyfr.discourse.group/t/making-a-pull-request-to-pyfr-on-github/297/1 "2020-09-22T15:21:43Z")

</div>

Is there a certain workflow that people should follow to contribute to PyFR on GitHub? I noticed the repository shows the `develop` branch by default. Should Pull Requests be made to the `develop` branch or to the `master` branch?

---

<div class="post-metadata">

**Author:** ![fdw](https://avatars.discourse-cdn.com/v4/letter/f/a587f6/32.png) [@fdw](https://pyfr.discourse.group/u/fdw)\
**Post date:** [23 September 2020 02:36 UTC](https://pyfr.discourse.group/t/making-a-pull-request-to-pyfr-on-github/297/2 "2020-09-23T02:36:39Z")

</div>

Hi Gavin,

We make use of the “git flow” model whereby PR’s are first merged into the develop branch. Then, when we want to bring forth a release we create a suitable RC branch off of develop, and once we are happy with it, merge it into master. As such master always points to the latest stable release.

Regards, Freddie.

---

<div class="post-metadata">

**Author:** ![Gavin\_Wiggins](https://avatars.discourse-cdn.com/v4/letter/g/cdc98d/32.png) [@Gavin\_Wiggins](https://pyfr.discourse.group/u/Gavin_Wiggins)\
**Post date:** [23 September 2020 21:20 UTC](https://pyfr.discourse.group/t/making-a-pull-request-to-pyfr-on-github/297/3 "2020-09-23T21:20:15Z")

</div>

Freddie,

As you suggested, I submitted a Pull Request to the `develop` branch [https://github.com/PyFR/PyFR/pull/170](https://github.com/PyFR/PyFR/pull/170). It’s just some documentation related to the examples. If you have any questions, you can ask them on GitHub within the Pull Request.

Thanks,  
Gavin
