-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Always show usernames in reaction tooltips #26444
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
silverwind
merged 3 commits into
go-gitea:main
from
n0toose:show-usernames-in-reactions
Aug 10, 2023
Merged
Always show usernames in reaction tooltips #26444
silverwind
merged 3 commits into
go-gitea:main
from
n0toose:show-usernames-in-reactions
Aug 10, 2023
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
Even if GetDisplayName() is normally preferred elsewhere, this change provides more consistency, as usernames are also always being shown when participating in a conversation taking place in an issue or a pull request. This change makes conversations easier to follow, as you would not have to have a mental association between someone's username and someone's real name in order to follow what is happening. This behavior matches GitHub's. Optimally, both the username and the full name (if applicable) could be shown, but such an effort is a much bigger task that needs to be thought out well.
silverwind
approved these changes
Aug 10, 2023
Shouldn't pass locally :)
|
delvh
approved these changes
Aug 10, 2023
That's because I did |
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Aug 11, 2023
* upstream/main: Update upgrade documentation to add a check for deprecated configurations (go-gitea#26451) Fall back to esbuild for css minify (go-gitea#26445) Update JS dependencies (go-gitea#26449) Call git.InitSimple for runRepoSyncReleases (go-gitea#26396) Target specific OS for devcontainer base image (go-gitea#26422) Lock go to 1.21 on CI (go-gitea#26433) Always show usernames in reaction tooltips (go-gitea#26444) Fix incorrect redirection in new issue using references (go-gitea#26440) Fix the display of orgs listed in user profile (go-gitea#26424) minio: add missing region on client initialization (go-gitea#26412) Fix wrong middleware sequence (go-gitea#26428)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
lgtm/done
This PR has enough approvals to get merged. There are no important open reservations anymore.
type/enhancement
An improvement of existing functionality
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.
Even if GetDisplayName() is normally preferred elsewhere, this change
provides more consistency, as usernames are also always being shown
when participating in a conversation taking place in an issue or
a pull request. This change makes conversations easier to follow, as
you would not have to have a mental association between someone's
username and someone's real name in order to follow what is happening.
This behavior matches GitHub's. Optimally, both the username and the
full name (if applicable) could be shown, but such an effort is a
much bigger task that needs to be thought out well.