This breaks compatibility with small repositories where there is file renaming #10274

New Issue

2025-11-02T09:02:55-06:00

GiteaMirror commented

2025-11-02 09:02:55 -06:00

Originally created by @lunny on GitHub (Feb 15, 2023).

This breaks compatibility with small repositories where there is file renaming

Originally posted by @bvp in https://github.com/go-gitea/gitea/issues/20764#issuecomment-1430987108

@bvp

Originally created by @lunny on GitHub (Feb 15, 2023). This breaks compatibility with small repositories where there is file renaming _Originally posted by @bvp in https://github.com/go-gitea/gitea/issues/20764#issuecomment-1430987108_ @bvp

GiteaMirror added the type/bug label 2025-11-02 09:02:55 -06:00

GiteaMirror commented

2025-11-02 09:02:55 -06:00

@moseslecce commented on GitHub (May 16, 2023):

Wouldn't it be best to offer this as a setting, perhaps per repo, where the administrator can decide if there is value to have this flag on or off (to decide if they want performance or a full historical view of changes)?

Alternatively github offers a link to show extended history

@moseslecce commented on GitHub (May 16, 2023): Wouldn't it be best to offer this as a setting, perhaps per repo, where the administrator can decide if there is value to have this flag on or off (to decide if they want performance or a full historical view of changes)? Alternatively [github offers a link to show extended history](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/)

GiteaMirror commented

2025-11-02 09:02:56 -06:00

@martin-tag24 commented on GitHub (Jun 9, 2023):

Wouldn't it be best to offer this as a setting, perhaps per repo, where the administrator can decide if there is value to have this flag on or off (to decide if they want performance or a full historical view of changes)?

Alternatively github offers a link to show extended history

Yes please make --follow as repo setting or add it as option to the api and commits list.

@martin-tag24 commented on GitHub (Jun 9, 2023): > Wouldn't it be best to offer this as a setting, perhaps per repo, where the administrator can decide if there is value to have this flag on or off (to decide if they want performance or a full historical view of changes)? > > Alternatively [github offers a link to show extended history](https://github.blog/changelog/2022-06-06-view-commit-history-across-file-renames-and-moves/) Yes please make `--follow` as repo setting or add it as option to the api and commits list.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#10274