Project

General

Profile

Task #4280

Shadow-repo behaviour

Added by Marcin Kuzminski [CTO] almost 4 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
14.10.2016
Due date:
% Done:

0%

Estimated time:
Sorting:
Commit Number:

Description

We have an exposure of shadow-repos. I kept on wondering what the outcome of shadow repos should be.

We have a different merge strategies, I think the shadow repo should solmehow reflect that if possible. However since the strategy could be use during the merge it means basically
we cannot make it pre-action.

Then i think we should always do a merge inside a shadow repo to reflect the final state of the code. In my view if merge is succesful a rebase or squash and rebase would be as well.

Currently i seen that git exposes a merged state, while Mercurial not.


Related issues

Related to RhodeCode CE/EE - Feature #1055: [pr, vcs] Expose the shadow repository of a pull requestResolved2015-02-05

History

#1 Updated by Marcin Kuzminski [CTO] almost 4 years ago

  • Related to Feature #1055: [pr, vcs] Expose the shadow repository of a pull request added

#2 Updated by Marcin Kuzminski [CTO] almost 4 years ago

  • Status changed from New to Rejected

as discussed we found a neet solution and it's implemented in parent task already

Also available in: Atom PDF