# Being friendly to quick contributions

**URL:** <https://swi-prolog.discourse.group/t/being-friendly-to-quick-contributions/493>\
**Category:** General\
**Created:** [April 5, 2019, 7:00pm UTC](https://swi-prolog.discourse.group/t/being-friendly-to-quick-contributions/493 "2019-04-05T19:00:47Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\
**Post date:** [July 7, 2019, 7:34am UTC](https://swi-prolog.discourse.group/t/being-friendly-to-quick-contributions/493/6 "2019-07-07T07:34:18Z")

</div>

Thanks for the patch. Applied. To make a pull request for a package,

- Clone the main repo (swipl-devel.git)
- Init the packages (using one of the ways you describe)
- Go to the package
- run `git checkout master && git pull`
- branch: `git checkout -b myfix`
- Hack away and commit

So far all is pretty normal. Now we come to the special part …

- Fork the package at github, creating e.g. `git@github.com:me/packages-clib.git`
- Run (from the clib checked out dir)
  - `git remote add fork git@github.com:me/packages-clib.git`
  - `git push fork myfix:myfix`

Now create a PR at github.

But, good old git patches are just as easy to handle for me, so what you did is perfectly fine.

The website content is in the repo `plweb-www.git`

---

_[View the full topic](https://swi-prolog.discourse.group/t/being-friendly-to-quick-contributions/493)._