Project

General

Profile

Bug #2069

Checking out FETCH_HEAD leads to unexpected results in case of only new tags

Added by Henning Blohm over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
z2-core
Target version:
Start date:
05.05.2020
Due date:
% Done:

0%

Estimated time:
origin:

Description

The current GitCR Implementation uses a fetch ref spec +<X>:<X> to fetch the requested Git source and then checks out FETCH_HEAD, as that showed to be more robust in case X==HEAD.

However, when there are no other changes and as we fetch tags as well, FETCH_HEAD may point to the latest tag instead.

Also previous experiments have shown that fetching +HEAD:HEAD and checking out HEAD is not reliable as well.

Acceptance Criteria

  • We have an artificial ref Z2_HEAD and
    • if X==HEAD we fetch +HEAD:_Z2_HEAD_ and check out Z2_HEAD
    • if X!=HEAD we fetch +X:X and check out X
#1

Updated by Henning Blohm over 1 year ago

  • Description updated (diff)
#2

Updated by Henning Blohm over 1 year ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF