github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-18 00:14:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

git-blame view does not show profile icons correctly #4266

New Issue
Closed
opened 2025-11-02 05:44:17 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 05:44:17 -06:00
Owner
Copy Link

Originally created by @hapasa on GitHub (Nov 7, 2019).

  • Gitea version (or commit ref): 1.10
  • Git version: 1.8.3.1
  • Operating system: Red Hat Enterprise Linux Server release 7.6 (Maipo)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • [X ] Not relevant
  • Log gist:

Description

If in settings

DISABLE_GRAVATAR = true
ENABLE_FEDERATED_AVATAR = true

the git-blame view will display generic coffee cup avatar, while it the Dashboards the local avatar is correctly displayed.

In git-blame:
<img class="ui avatar image" src="/img/avatar_default.png" title="Harri">

In Dashboard:
<img class="ui avatar image" src="/user/avatar/harri/-1" alt="">

...

Screenshots

image

image

Originally created by @hapasa on GitHub (Nov 7, 2019). - Gitea version (or commit ref): 1.10 - Git version: 1.8.3.1 - Operating system: Red Hat Enterprise Linux Server release 7.6 (Maipo) - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X ] Not relevant - Log gist: ## Description If in settings DISABLE_GRAVATAR = true ENABLE_FEDERATED_AVATAR = true the git-blame view will display generic coffee cup avatar, while it the Dashboards the local avatar is correctly displayed. In git-blame: `<img class="ui avatar image" src="/img/avatar_default.png" title="Harri">` In Dashboard: `<img class="ui avatar image" src="/user/avatar/harri/-1" alt="">` ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![image](https://user-images.githubusercontent.com/8208561/68400545-822e5800-0178-11ea-8e57-5595d2f0fa5a.png) ![image](https://user-images.githubusercontent.com/8208561/68400682-b6a21400-0178-11ea-8825-b238bfefbb64.png)
GiteaMirror added the issue/staleissue/needs-feedback labels 2025-11-02 05:44:17 -06:00
GiteaMirror commented 2025-11-02 05:44:18 -06:00
Author
Owner
Copy Link

@mrsdizzie commented on GitHub (Nov 7, 2019):

Do you have a full example you can link to? The main reason this would happen is if that particular commit you cropped in the screenshot has a different e-mail address than the user with the icon

@mrsdizzie commented on GitHub (Nov 7, 2019): Do you have a full example you can link to? The main reason this would happen is if that particular commit you cropped in the screenshot has a different e-mail address than the user with the icon
GiteaMirror commented 2025-11-02 05:44:18 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Nov 7, 2019):

Per the Discord conversation it seems this was caused by emails not matching.

@jolheiser commented on GitHub (Nov 7, 2019): Per the Discord conversation it seems this was caused by emails not matching.
GiteaMirror commented 2025-11-02 05:44:18 -06:00
Author
Owner
Copy Link

@hapasa commented on GitHub (Nov 8, 2019):

Indeed it was email address mismatch. However, it was not at all obvious to sort out, especially since in the Dashboard the correct avatar was showing.

@hapasa commented on GitHub (Nov 8, 2019): Indeed it was email address mismatch. However, it was not at all obvious to sort out, especially since in the Dashboard the correct avatar was showing.
GiteaMirror commented 2025-11-02 05:44:18 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 8, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 8, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback issue/stale
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#4266
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?