atlassian / atlassian/atlascode
How to leverage upstream repos when working on forks
Open
bitbucket
DC
- Dominant language
- TypeScript
- Stars
- 129
- Forks
- 82
- Avg merge
- 3h 3m
- Merged PRs (30d)
- 6
Description
We are self-hosting bitbucket, and I have been able to configure it to use my repo.
The problem is that I only see pull requests in my fork and not in the upstream repo for it.
Any ideas how I fix this?
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reproducing the self-hosted Bitbucket setup and comparing pull-request discovery for the fork and its upstream repository; done means the expected upstream pull requests appear in AtlasCode or the limitation and required configuration are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100