PostHog Code creating PRs and reports on wrong repository
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
PostHog Code is automatically creating PRs and inbox reports targeting the wrong GitHub repository. I've verified my GitHub account connection in PostHog Code settings, but the issue persists.
Details:
Working locally (not cloud tasks)
Issue occurs with signal/inbox reports
When I try to create a PR from a report, it targets the incorrect repository
I've connected the correct GitHub account in PostHog Code settings
What I've tried:
Connected the correct GitHub account in PostHog Code settings
Verified I've "setup the right one everywhere" in my configuration
What I need help with:
How to configure the default/correct repository for inbox reports
How to change the target repository for existing reports that are already created
Where in the settings I can control repository selection for auto-generated PRs
Environment:
PostHog Code (desktop app)
Working locally
Self-driving inbox with signal sources enabled
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the PostHog Code desktop app settings and reproduce the issue with a local self-driving inbox using signal sources. Trace how an inbox report selects its repository when creating a PR; done means new reports target the configured repository and the behavior for existing reports is clear or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100