Hi, This is our team situation.
Each of team members fork the A repo.
They make pull request to A repo's main branch from their own forked repo's branch when they finish development.
And we go on code review and merge in to A repo's main branch.
The thing I want to do is automation in Jira.
And let's say there's four states in issue.
- Open, In-progress, Resolved, ReadyForQA
So I just make three automation rules.
1. when branch created from each of team memeber's forked repo and push to their own forked repo, move issue to In-progress
2. when Pull request created from forked repo to A repo, move issue to Resolved
3. when Pull request merged to A repo, move issue to ReadyForQA
I found out that 2, 3 automation rules worked when I make automations like this screen captures.
.
But the problem is first rule. I made it like under screen capture.
.
It worked when I made branch and push from A repo, not A repo's forked repo.
So I just want to know how to transition the issue from open → In-progress when we use fork repository.
Is there any automation trigger for github forked repo or any other way to catch these push from forked repository?
Hello @YeonJeongMin ,
I'm not too sure of the use case you're mentioning, but in my view, when we create a FORK, we are essentially drifting away from the main repo, unlike branching. Since Jira doesn't track FORK by default you can perhaps build a custom solution around this.
In theory, you can trigger a webhook from github when you create a FORK, (https://docs.github.com/en/webhooks-and-events/webhooks/webhook-events-and-payloads#fork).
The blog is a bit old but might be relevant for your use case.
Thank you for your quick reply @Jehan Bhathena :)
I understand that there's no default way to track FORK repo.
I will find out the way to webhook the branch push from my FORK repo following the steps you give me references.
Thanks 👍🏻
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.