on 06 Aug, 2022 11:02 AM
I guess, it's what you're defining a virtual PR commit.
The problem can be seen on this pull request not working vs this one working.
Here is the scenario for the PR not working
I work on a dedicate feature branch and push some code
The appVeyor build is started, build successful and the build is pushing some documentation updates back to git
A second appVeyor build is not started because the push is on the directory docs/
(steps 2 and 3 are executed twice)
Until this point everything is working as I was expected.
But then I create a pull request on GitHub. The main branch is protected so I won't be able to merge before the following three checks are successful:
GitGuardian (out-of-scope for this discussion)
A branch build
A PR build (I guess it's what you're naming a virtual commit)
But the two builds are not starting because (I guess) the last commit is on the folder docs/ ... which is excluded by skip_commits. This is what I'm trying to workaround. I'd like that, at least, the PR build is starting. It's not a bug, I fully understand why appVeyor is taking the decision to not start the build, I'm just asking if there is a way to workaround this.
When I forced the merge on the main branch with a rebase and squash, the squashed commit to the main branch was touching both the code and the docs/ folder, so no problem the build started.