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

Wrong latest-commit displayed in repo subdirectories #7049

New Issue
Closed
opened 2025-11-02 07:14:25 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 07:14:25 -06:00
Owner
Copy Link

Originally created by @noerw on GitHub (Mar 22, 2021).

  • Gitea version (or commit ref): 1.14.0-RC1
  • Git version: 2.30.2
  • Operating system: linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No

Description

The last-commit header always shows the very latest commit, not the last commit within the viewed directory, as it did in 1.13.x

Screenshots

grafik

Originally created by @noerw on GitHub (Mar 22, 2021). - Gitea version (or commit ref): 1.14.0-RC1 - Git version: 2.30.2 - Operating system: linux <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) - [ ] No - [ ] ## Description The last-commit header always shows the very latest commit, not the last commit within the viewed directory, as it did in 1.13.x ## Screenshots ![grafik](https://user-images.githubusercontent.com/7880552/112012238-ef9a1900-8b20-11eb-9c70-f52ca08cd237.png)
GiteaMirror added the issue/regressiontype/bug labels 2025-11-02 07:14:25 -06:00
GiteaMirror commented 2025-11-02 07:14:26 -06:00
Author
Owner
Copy Link

@noerw commented on GitHub (Sep 20, 2021):

this is fixed in version 1.16.0+dev-191-g9b4280ea4 by an unknown change

@noerw commented on GitHub (Sep 20, 2021): this is fixed in version 1.16.0+dev-191-g9b4280ea4 by an unknown change
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/regression type/bug
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#7049
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?