Fix Actions pull_request.paths being triggered incorrectly by rebase
#36045
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
GiteaBot
added
the
lgtm/need 2
Zettat123
changed the title
push.paths being triggered incorrectly by rebasepull_request.paths being triggered incorrectly by rebase
Zettat123
force-pushed
the
actions-pr-path-rebase
branch
from
1211df2 to
120b574
Compare
lunny
approved these changes
Nov 28, 2025
GiteaBot
added
lgtm/need 1
silverwind
approved these changes
Nov 28, 2025
GiteaBot
added
lgtm/done
silverwind
added
the
reviewed/wait-merge
GiteaBot
removed
the
reviewed/wait-merge
Zettat123
added a commit
to Zettat123/gitea
that referenced
this pull request
Nov 28, 2025
go-gitea#36045) Partially fix go-gitea#34710 The bug described in go-gitea#34710 can be divided into two parts: `push.paths` and `pull_request.paths`. This PR fixes the issue related to `pull_request.paths`. The root cause is that the check for whether the workflow can be triggered happens **before** updating the PR’s merge base. This causes the file-change detection to use the old merge base. Therefore, we need to update the merge base first and then check whether the workflow can be triggered.
lunny
pushed a commit
that referenced
this pull request
Nov 29, 2025
#36045) (#36054) Backport #36045 Partially fix #34710 The bug described in #34710 can be divided into two parts: `push.paths` and `pull_request.paths`. This PR fixes the issue related to `pull_request.paths`. The root cause is that the check for whether the workflow can be triggered happens **before** updating the PR’s merge base. This causes the file-change detection to use the old merge base. Therefore, we need to update the merge base first and then check whether the workflow can be triggered.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Partially fix #34710
The bug described in #34710 can be divided into two parts:
push.pathsandpull_request.paths. This PR fixes the issue related topull_request.paths. The root cause is that the check for whether the workflow can be triggered happens before updating the PR’s merge base. This causes the file-change detection to use the old merge base. Therefore, we need to update the merge base first and then check whether the workflow can be triggered.