# Issues and pull requests

**URL:** <https://support.prodi.gy/t/issues-and-pull-requests/156>\
**Category:** Uncategorized\
**Tags:** meta\
**Created:** [December 23, 2017, 5:04pm UTC](https://support.prodi.gy/t/issues-and-pull-requests/156 "2017-12-23T17:04:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wpm](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/wpm/32/103_2.png) [@wpm](https://support.prodi.gy/u/wpm)\
**Post date:** [December 23, 2017, 5:04pm UTC](https://support.prodi.gy/t/issues-and-pull-requests/156/1 "2017-12-23T17:04:24Z")

</div>

How should we submit bugs or suggested new code to Prodigy? It doesn’t have a repo under [Explosion AI’s github area](https://github.com/explosion), which I’m assuming is because this is a commercial product.

---

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [December 23, 2017, 11:06pm UTC](https://support.prodi.gy/t/issues-and-pull-requests/156/2 "2017-12-23T23:06:40Z")

</div>

Yes, that’s a good point – thanks for bringing this up! The current plan is to use the forum as an issue tracker and general support channel and to open-source the recipes as a separate `prodigy-recipes` repository on GitHub. We should be able to get this all ready after the holidays 😊

We were thinking about organising the public recipes into separate directories – one for the built-ins, one for additional or more specific recipes and examples, and maybe one for community recipes. This would let users make pull requests to the built-in recipes – if you end up writing a cool recipe for a specific use case and want to share it with others, you can submit it to the repo as well.