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

Detection of renamed files not working with Git 1.9.1 #50

New Issue
Closed
opened 2025-11-02 03:06:00 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 03:06:00 -06:00
Owner
Copy Link

Originally created by @jhasse on GitHub (Nov 10, 2016).

  • Gitea version (or commit ref): 0.9.99.0903
  • Git version: 1.9.1
  • Operating system: Ubuntu 14.04.5 LTS
  • Database:
    • PostgreSQL
    • MySQL
    • SQLite

Description

I have a commit with a file A which get's renamed to B. Instead of showing that, Gogs/Gitea just shows me A with all it content removed and added again.

This Gogs commit added support for detecting file renames: bc82157216

I couldn't reproduce this on https://try.gogs.io, so I think it has something to do with my older Git version.

Originally created by @jhasse on GitHub (Nov 10, 2016). - Gitea version (or commit ref): 0.9.99.0903 - Git version: 1.9.1 - Operating system: Ubuntu 14.04.5 LTS - Database: - [ ] PostgreSQL - [x] MySQL - [ ] SQLite ## Description I have a commit with a file A which get's renamed to B. Instead of showing that, Gogs/Gitea just shows me A with all it content removed and added again. This Gogs commit added support for detecting file renames: https://github.com/go-gitea/gitea/commit/bc8215721627fcdeaa23c6e3bf625e0c4e5c3407 I couldn't reproduce this on https://try.gogs.io, so I think it has something to do with my older Git version.
GiteaMirror added the issue/not-a-bug label 2025-11-02 03:06:00 -06:00
GiteaMirror commented 2025-11-02 03:06:01 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Nov 12, 2016):

The commit you reference is already also in Gitea. Can you reproduce locally ?
Non-reproducible bugs would be nearly impossible to fix. Ideally a failing automated test would be provided, can you try that ?

@strk commented on GitHub (Nov 12, 2016): The commit you reference is already also in Gitea. Can you reproduce locally ? Non-reproducible bugs would be nearly impossible to fix. Ideally a failing automated test would be provided, can you try that ?
GiteaMirror commented 2025-11-02 03:06:01 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Nov 12, 2016):

Ideally a failing automated test would be provided, can you try that ?

How could he provide a failing test with specific Git versions?

@tboerger commented on GitHub (Nov 12, 2016): > Ideally a failing automated test would be provided, can you try that ? How could he provide a failing test with specific Git versions?
GiteaMirror commented 2025-11-02 03:06:01 -06:00
Author
Owner
Copy Link

@jhasse commented on GitHub (Nov 14, 2016):

How could he provide a failing test with specific Git versions?

I could set up a Dockerfile.

Is there an automated test for file renames?

@jhasse commented on GitHub (Nov 14, 2016): > How could he provide a failing test with specific Git versions? I could set up a Dockerfile. Is there an automated test for file renames?
GiteaMirror commented 2025-11-02 03:06:01 -06:00
Author
Owner
Copy Link

@strk commented on GitHub (Nov 14, 2016):

I don't think there's an automated test for file renames. Such test would be enough, then the testers would have to deal with different Git versions.

@strk commented on GitHub (Nov 14, 2016): I don't think there's an automated test for file renames. Such test would be enough, then the _testers_ would have to deal with different Git versions.
GiteaMirror commented 2025-11-02 03:06:02 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Nov 14, 2016):

@strk testers (as in Drone) should test using different git-versions yes 😉

@bkcsoft commented on GitHub (Nov 14, 2016): @strk _testers_ (as in Drone) should test using different git-versions yes :wink:
GiteaMirror commented 2025-11-02 03:06:02 -06:00
Author
Owner
Copy Link

@bkcsoft commented on GitHub (Nov 14, 2016):

@jhasse

I think it has something to do with my older Git version.

Please try that first 😉

@bkcsoft commented on GitHub (Nov 14, 2016): @jhasse > I think it has something to do with my older Git version. Please try that first :wink:
GiteaMirror commented 2025-11-02 03:06:02 -06:00
Author
Owner
Copy Link

@jhasse commented on GitHub (Nov 14, 2016):

I couldn't reproduce with git version 2.7.4. I'll try again with a virtual machine, might take a while ...

@jhasse commented on GitHub (Nov 14, 2016): I couldn't reproduce with git version 2.7.4. I'll try again with a virtual machine, might take a while ...
GiteaMirror commented 2025-11-02 03:06:02 -06:00
Author
Owner
Copy Link

@jhasse commented on GitHub (Nov 18, 2016):

Okay I've could not reproduce, even with the older Git version :( There seems to be something special about that commit, maybe I have time to create a minimal example. I would create a new bug report then.

@jhasse commented on GitHub (Nov 18, 2016): Okay I've could not reproduce, even with the older Git version :( There seems to be something special about that commit, maybe I have time to create a minimal example. I would create a new bug report then.
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/not-a-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#50
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?