AL-Go version
9.0
Describe the issue
Hi I 've got a strange issue on one of our repos.
One of my developers made a hotfix to the release branch and that worked fine.
He then had a new piec of work to do and did that in the same hotfix branch and created a PR into Main, I spotted this and the check failed as there was a merge conflict I told him to remove the extra change, rebase the feature branch onto origin/main and create a PR into Main.
When he did this which I watched, the Pull Request didn't trigger the Pull Request Build.
He then created a second branch from origin/main and made the changes for the new functionality he had done committed these and created a PR on GitHub to Main, again the Pull Request Build didn't trigger.
He then created another new branch based on origin/main and did some new work. He has then committed this and created a PR on Gitub and this one the Pull Request Build has triggered.
These three have all been in the same repo and no other work has been done since the creation of the 3 PRs.
I have seen that in v9 of AL-Go the trigger for the Pull Request Build workflow changed from pull_request_target to Pull_request and the help on this says the workflow won't run if there is a merge conflict but when I look there isn't any merge conflicts.
Looking at the 3 PRs I can't see any thing different between the 2 that haven't triggered the workflow compared to the one that did trigger it.
The PR messages for the 2 that didn't trigger are:
- RITM0499014 Credit Memo Start End Date Change request
- RITM0480068 DD SalesInvoice
The first one the head commit has the same message the second one has the message:
- Change Request related to sales invoice report to show DD text if DD Mandate ID is having value on SI
Expected behavior
For the Pull Request Build workflow to run
Steps to reproduce
I'm not sure as what seem like the same steps sometimes work and other times doesn't as explained above
Additional context (logs, screenshots, etc.)
I can't find any logs that would indicate why the workflow didn't run
AL-Go version
9.0
Describe the issue
Hi I 've got a strange issue on one of our repos.
One of my developers made a hotfix to the release branch and that worked fine.
He then had a new piec of work to do and did that in the same hotfix branch and created a PR into Main, I spotted this and the check failed as there was a merge conflict I told him to remove the extra change, rebase the feature branch onto origin/main and create a PR into Main.
When he did this which I watched, the Pull Request didn't trigger the Pull Request Build.
He then created a second branch from origin/main and made the changes for the new functionality he had done committed these and created a PR on GitHub to Main, again the Pull Request Build didn't trigger.
He then created another new branch based on origin/main and did some new work. He has then committed this and created a PR on Gitub and this one the Pull Request Build has triggered.
These three have all been in the same repo and no other work has been done since the creation of the 3 PRs.
I have seen that in v9 of AL-Go the trigger for the Pull Request Build workflow changed from pull_request_target to Pull_request and the help on this says the workflow won't run if there is a merge conflict but when I look there isn't any merge conflicts.
Looking at the 3 PRs I can't see any thing different between the 2 that haven't triggered the workflow compared to the one that did trigger it.
The PR messages for the 2 that didn't trigger are:
The first one the head commit has the same message the second one has the message:
Expected behavior
For the Pull Request Build workflow to run
Steps to reproduce
I'm not sure as what seem like the same steps sometimes work and other times doesn't as explained above
Additional context (logs, screenshots, etc.)
I can't find any logs that would indicate why the workflow didn't run