Skip to content

Fix wrong review requests when updating the pull request #34286

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 28, 2025

Conversation

lunny
Copy link
Member

@lunny lunny commented Apr 25, 2025

Fix #34224

The previous implementation in #33744 will get the pushed commits changed files. But it's not always right when push a merged commit. This PR reverted the logic in #33744 and will always get the PR's changed files and get code owners.

@lunny lunny added type/bug backport/v1.23 This PR should be backported to Gitea 1.23 labels Apr 25, 2025
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Apr 25, 2025
@github-actions github-actions bot added the modifies/go Pull requests that update Go code label Apr 25, 2025
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Apr 28, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Apr 28, 2025
@lunny lunny enabled auto-merge (squash) April 28, 2025 22:28
@lunny lunny added this to the 1.24.0 milestone Apr 28, 2025
@lunny lunny merged commit 44d7d29 into go-gitea:main Apr 28, 2025
26 checks passed
GiteaBot pushed a commit to GiteaBot/gitea that referenced this pull request Apr 28, 2025
)

Fix go-gitea#34224

The previous implementation in go-gitea#33744 will get the pushed commits
changed files. But it's not always right when push a merged commit. This
PR reverted the logic in go-gitea#33744 and will always get the PR's changed
files and get code owners.
@GiteaBot GiteaBot added the backport/done All backports for this PR have been created label Apr 28, 2025
@lunny lunny deleted the lunny/fix_wrong_review_request branch April 28, 2025 23:05
lunny added a commit that referenced this pull request Apr 29, 2025
…4304)

Backport #34286 by @lunny

Fix #34224

The previous implementation in #33744 will get the pushed commits
changed files. But it's not always right when push a merged commit. This
PR reverted the logic in #33744 and will always get the PR's changed
files and get code owners.

Co-authored-by: Lunny Xiao <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/done All backports for this PR have been created backport/v1.23 This PR should be backported to Gitea 1.23 lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. modifies/go Pull requests that update Go code type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CODEOWNERS trigger on PR update also activated by merge commit
4 participants