GitHub Pull Requests - Multiple Projects In A Solution
Is there a way to make appveyor build based on the merge commit instead of the head commit for pull requests?
If I have two appveyor.yml files one for "Project A" and one for "Project B" I can setup the "only_commits: files:" to only start the build for the projects that are modified.
If I create a pull request on GitHub with Project A modifed it will run the build for Project A. If I add a commit with Project B modified to that PR it will build Project B but not show the status for Project A as a status check anymore. Is it possible to have the appveyor build check the merge commit instead of the head commit for these commit filters so that both A and B would be built for the last commit (since the PR modified both)?
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 10 Mar, 2022 05:29 PM
You can set "Custom commit status context" on General tab of project settings to have project-specific build checks.
2 Posted by bterry18 on 10 Mar, 2022 06:00 PM
I have already setup the "Custom commit status context" for both builds so that the status checks show. The issue is that if I had project A, B, C in a single GitHub repository and the PR only modified A and B I would only like the build/tests for A and B to run not C. Currently the only way I can think to do that is to use:
"only_commits:
files: ProjectA/"
and another for B
but this seems to only work for the last commit of the PR. The only solution I think that is possible for me currently is to setup a single CI build that runs tests for all of the projects (A,B,C) and then add a build per project that deploys based on the commits so that only A and B would get deployed when the PR is squashed and merged into the main branch.
3 Posted by bterry18 on 10 Mar, 2022 06:59 PM
This issue from 2017 seems similar with what we are running into / trying to accomplish: https://github.com/appveyor/ci/issues/1923#issuecomment-537281418