atlassian / atlassian/github-for-jira
Tracking Branches on Forks
- Dominant language
- No language data
- Stars
- 655
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Description
_Sorry if this has been asked / answered, I did look through the issues and though some seem related they're not exactly our use case._
On our team each dev has their own fork of our main repo. They work off that fork creating branches and then PRs targeting our main repo. While this integration picks up the PRs and associates with the issue, and at _that_ point it picks up the branch, it doesn't seem to pick up branches on the forks just created using the naming convention (just copied the CLI branch command to test).
And as far as I can tell #402 has been implemented, but also gives no way to create the branch on a fork. I just want to confirm that this is likely _not_ something that will be supported. My goal is a dev creating a branch and pushing to their own fork could move the Jira issue to in progress and assign it to them. But it's not a huge issue if that's not possible.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing issue #402 and the integration behavior described here for branches created on GitHub forks. Determine whether a fork branch can trigger the desired Jira transition and assignment without a pull request; done means documenting the supported behavior or defining the required fork-tracking change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 15/100