Using skip_commit/files except for PR?
Is it possible to use the the feature skip_commits (files) but exclude this settings for PR?
My use-case is the following:
- my appVeyor build agent is automatically generating some documentation (during the on_success) - If updated, this documentation is pushed to the git repository by the appVeyor build agent - I don't want that this push is restarting a new build so I'm excluding the repository where I push documentation in the skip_files - This is working for me except after a pull request. If the last commit was a documentation update the appVeyor build agent won't start.
I'd like to be able to start the appVeyor build agent on these cases (PR) because I want to protect my main branch and add checks on GitHub that the PR is successfully building (currently stuck because the build doesn't start).
skip_commits:
files:
- docs/
- misc/
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 06 Aug, 2022 12:25 AM
By "PR" do you mean "while you are working on the PR, i.e. build of a virtual PR commit" or "build of a PR merge commit into 'main' branch"?
2 Posted by Cédric Charlier 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
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:
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.