Project

General

Profile

Actions

Defect #22010

closed

Git: Outdated Commits are not existing anymore, but are saved in Redmines cache

Added by Benjamin Schunn about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
SCM
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate
Affected version:

Description

At the bottom right, I can see all commits related to an issue. I'm using Git with Redmines redmine_git_hosting plugin in combination with gitolite. This is working great except the following scenario:
Commit some changes to the local repo with a message like "test test IssueID #22" and push it to origin master using this command: "git push origin master". Afterwards change the commits message on the local repo with "git rebase -i". Try to push this to origin master, it won't work (this is a correct behavior). To force the push use "git push origin master -f" and the commit will be pushed. You can see the new revision hash in the repository view and all seems to be good. But if you look in that related issues view, you can see the first commit AND the rebased commit. If you rebase your commits several Times, this could cause an undefined number of commits that are not exist anymore related to several issues.

So the first commit does not exist anymore and it seems that redmine is using some cache mechanism to persist that commit information. I know I can remove the relation of the first commit to that issue, by click on the firsts commit hash and click on the anchor removal icon. But I want to remove the whole set of outdatet commits which are obsolete by rebase.


Related issues

Is duplicate of Redmine - Feature #12853: Removing git branch result of database inconsistenciesNew

Actions
Actions #1

Updated by Toshi MARUYAMA about 8 years ago

  • Category changed from Hook requests to SCM
Actions #2

Updated by Toshi MARUYAMA about 8 years ago

  • Subject changed from Outdated Commits are not existing anymore, but are saved in Redmines cache to Git: Outdated Commits are not existing anymore, but are saved in Redmines cache
Actions #3

Updated by Toshi MARUYAMA about 8 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Duplicate of #12853.

Actions #4

Updated by Toshi MARUYAMA about 8 years ago

  • Is duplicate of Feature #12853: Removing git branch result of database inconsistencies added
Actions #5

Updated by Benjamin Schunn about 8 years ago

I think its a duplicate of #1273 not of #12853

sry for posting a new one, was not able to find something with my keywords.

Actions

Also available in: Atom PDF