You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@tjlytle Hey mate, just so that I'm clear on the issue you're seeing, your developers are creating forks of your repo into their own user organizations and you want our app to be able to detect their changes?
@mboudreau sorry for dropping this. Yeah, just on their own github account. So our org has a repo (company/our_app) and as I work on it I push to my fork (tjlytle/our_app), and then create PRs from my fork to the upstream (company/our_app) repo.
I realize that's more similar to an open source project workflow, but it's what has worked well for us. We're likely open to changing things if it helps get better visibility though.
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.
The text was updated successfully, but these errors were encountered: