2021-04-01 03:31:32 +02:00
There are many ways to contribute to PostHog. We want to help developers know exactly how users are interacting with their stuff, in a way that doesn't send data to 3rd parties.
2020-02-20 01:18:54 +01:00
# Creating a PR
Just create a new pull request if you want to make an update.
2023-07-19 16:27:54 +02:00
We recommend you create an issue if one doesn't already exist, and continue the conversation on the issue to get more info/alignment on what to build.
2020-02-20 01:18:54 +01:00
2023-07-19 16:27:54 +02:00
For more information on how we review PRs, please refer to our [handbook ](https://posthog.com/handbook/engineering/how-we-review ).
2020-02-20 01:18:54 +01:00
# Issues
Spotted a bug? Has deployment gone wrong? Do you have user feedback? Raise an issue for the fastest response.
... or pick up and fix an issue if you want to do a Pull Request.
2022-09-05 12:28:13 +02:00
## Issues with paid features
We prefer not to accept external contributions for paid features. If you don't see the feature on your local build, it's most probably paid.
2020-02-20 01:18:54 +01:00
# Feature requests
Raise an issue for these and tag it as an Enhancement. We love every idea. Please give us as much context on the why as possible.
# Features
We don't, yet, have a prescriptive roadmap laid out.
As a rule of thumb - if it fits with helping developers understand product usage, we'll generally like it.
If you are at all unsure, just raise it as an enhancement issue first, and we'll very quickly respond.