CODEOWNERS functionality is only triggered when opening a PR, but not after changes #33490
Comments
|
This feels quite important to fix. CODEOWNERS feature can be used for audits about PR's that touch certain files. |
lunny
added a commit
that referenced
this issue
Mar 14, 2025
…33744) Fix #33490 It will only read the changed file on the pushed commits but not all the files of this PR. --------- Co-authored-by: wxiaoguang <[email protected]>
lunny
added a commit
to lunny/gitea
that referenced
this issue
Mar 28, 2025
…o-gitea#33744) Fix go-gitea#33490 It will only read the changed file on the pushed commits but not all the files of this PR. --------- Co-authored-by: wxiaoguang <[email protected]>
lunny
added a commit
that referenced
this issue
Mar 28, 2025
…33744) (#34045) Fix #33490 Backport #33744 It will only read the changed file on the pushed commits but not all the files of this PR. Co-authored-by: wxiaoguang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When a new PR is opened CODEOWNERS functionality is triggered, but afterwards changes in the PR don't trigger CODEOWNERS functionality again.
For example I have next CODEOWNERS:
If I change
file1.jsand open a new PR,user1will be assigned as a reviewer. Then I changefile2.jsin the same branch so the PR has 2 changed files:file1.jsandfile2.jsbut CODEOWNER offile2.js(user2) is not assigned as a reviewerGitea Version
1.23.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Not relevant
Database
None
The text was updated successfully, but these errors were encountered: