Skip to content

Change "rejected" to "changes requested" in 3rd party PR review notification #34481

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 1 commit into from
May 16, 2025

Conversation

s-weigand
Copy link
Contributor

@s-weigand s-weigand commented May 15, 2025

This PR changes 3rd party notifications wording on a PR review that requests changes and can be considered a follow up for #5858 to also fix #5857 in 3rd party notifications.

The difference in the actual notification would be the following:

- Pull request review rejected
+ Pull request review changes requested

While this is a simple string change at first look, it has a deeper UX meaning.

Motivation

We could observe that some developers are hesitant to press the "Request changes" button since their peers first see that their changes were rejected, thus a more appropriate wording that also falls in line with the meaning and UI would be beneficial.

Meaning

Pressing the Request changes button in a PR review means that as a reviewer you are willing to merge the general change in a PR if changes requested review comments are implemented.
Rejecting a PR on the other hand would be equivalent with closing it since that change isn't welcome at all (e.g. out of scope feature).

Sync with UI

The UI button says request changes and the other options

image

Considered Problems

This might break some automation for users who rely on string matching.

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label May 15, 2025
@github-actions github-actions bot added the modifies/go Pull requests that update Go code label May 15, 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 May 15, 2025
@lunny lunny added this to the 1.25.0 milestone May 15, 2025
@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 May 16, 2025
@techknowlogick techknowlogick changed the title 👌 Change "rejected" to "changes requested" in 3rd party PR review notification Change "rejected" to "changes requested" in 3rd party PR review notification May 16, 2025
@techknowlogick techknowlogick merged commit 7b518bc into go-gitea:main May 16, 2025
26 checks passed
@s-weigand s-weigand deleted the reword-notification branch May 16, 2025 07:36
zjjhot added a commit to zjjhot/gitea that referenced this pull request May 19, 2025
* giteaofficial/main:
  [skip ci] Updated translations via Crowdin
  Fix edithook api can not update package, status and workflow_job events (go-gitea#34495)
  Fix url validation in webhook add/edit API (go-gitea#34492)
  Add R-HNF to the TRANSLATORS file (go-gitea#34494)
  Add missing setting load in dump-repo command (go-gitea#34479)
  nix flake update (go-gitea#34476)
  Fix get / delete runner to use consistent http 404 and 500 status (go-gitea#34480)
  Change "rejected" to "changes requested" in 3rd party PR review notification (go-gitea#34481)
  Add migrations tests (go-gitea#34456)
  Fix project board view (go-gitea#34470)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Suggestion: rename "Reject" to "Request changes" (or similar)
5 participants