-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Fix null requested_reviewer from API #31773
Fix null requested_reviewer from API #31773
Conversation
Thanks for the contribution! I think it maybe better to create a separate array field in the DTO object for requested teams (similar to GitHub, see here). To me this makes more sense performance-wise (e.g. there can be many members in a team and, if I'm not mistaken, there may be multiple teams reviewing a PR; this is maybe too much data for us to send that consumers may not care much about). I guess it makes sense logically too since we aren't requesting a review from individual team members but rather the team as a whole. This shouldn't be a breaking change either. |
so you mean create a separate array in response object for teams right? And this array field returns teams information? 🤔 |
Yes |
then I think now better. Ready for review |
* giteaofficial/main: Fix protected branch files detection on pre_receive hook (go-gitea#31778) Add signature support for the RPM module (go-gitea#27069) Fix null requested_reviewer from API (go-gitea#31773)
If the assign the pull request review to a team, it did not show the members of the team in the "requested_reviewers" field, so the field was null. As a solution, I added the team members to the array.
fix #31764