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

PR Commit and Changed Files tab broken #5165

New Issue
Closed
opened 2025-11-02 06:16:37 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 06:16:37 -06:00
Owner
Copy Link

Originally created by @xoxys on GitHub (Apr 1, 2020).

  • Gitea version (or commit ref): 1.11.4
  • Operating system: CentOS 7
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite

Description

After upgrading to v1.11.3 the tabs for Commits and Changed Files are no longer accessible after a PR was merged.

Screenshot

grafik

Originally created by @xoxys on GitHub (Apr 1, 2020). - Gitea version (or commit ref): 1.11.4 - Operating system: CentOS 7 - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite ## Description After upgrading to v1.11.3 the tabs for `Commits` and `Changed Files` are no longer accessible after a PR was merged. ## Screenshot ![grafik](https://user-images.githubusercontent.com/3391958/78170660-93437280-7453-11ea-9c9a-cafb6cdaf825.png)
GiteaMirror commented 2025-11-02 06:16:38 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Apr 1, 2020):

Hi we've already fixed this with PR #10909. See #10766

There will be a migration that fixes these and other older problems in 1.12 - the code is in #10786

@zeripath commented on GitHub (Apr 1, 2020): Hi we've already fixed this with PR #10909. See #10766 There will be a migration that fixes these and other older problems in 1.12 - the code is in #10786
GiteaMirror commented 2025-11-02 06:16:38 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Apr 1, 2020):

Please upgrade to 1.11.4 where the issue is fixed.

@zeripath commented on GitHub (Apr 1, 2020): Please upgrade to 1.11.4 where the issue is fixed.
GiteaMirror commented 2025-11-02 06:16:38 -06:00
Author
Owner
Copy Link

@xoxys commented on GitHub (Apr 1, 2020):

@zeripath I am already on 1.11.4 as written in my first post and it is still broken for an existing PR as you could see in the screenshot

@xoxys commented on GitHub (Apr 1, 2020): @zeripath I am already on 1.11.4 as written in my first post and it is still broken for an existing PR as you could see in the screenshot
GiteaMirror commented 2025-11-02 06:16:38 -06:00
Author
Owner
Copy Link

@xoxys commented on GitHub (Apr 1, 2020):

Ok, it's fixed for new PR's but old broken PR's stay broken currently, right?

@xoxys commented on GitHub (Apr 1, 2020): Ok, it's fixed for new PR's but old broken PR's stay broken currently, right?
GiteaMirror commented 2025-11-02 06:16:39 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Apr 1, 2020):

Yup sorry about that they'll get fixed when the migrations in 1.12 run but you can manually fix.

@zeripath commented on GitHub (Apr 1, 2020): Yup sorry about that they'll get fixed when the migrations in 1.12 run but you can manually fix.
GiteaMirror commented 2025-11-02 06:16:39 -06:00
Author
Owner
Copy Link

@xoxys commented on GitHub (Apr 1, 2020):

No worries. I've just misunderstood that point 🙂

@xoxys commented on GitHub (Apr 1, 2020): No worries. I've just misunderstood that point 🙂
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
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#5165
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?