Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add chstream-action option #63

Open
orao opened this issue Apr 5, 2016 · 0 comments
Open

Add chstream-action option #63

orao opened this issue Apr 5, 2016 · 0 comments
Assignees
Milestone

Comments

@orao
Copy link
Collaborator

orao commented Apr 5, 2016

There is a number of things that we could map the chstream transaction to, none of which are ideal so allowing the end user to choose what happens might be best.

We could do a git rebase with some merge strategy, a git cherry-pick or git merge depending on what has happened and on what new commit we are basing our changes on.

The most accurate representation is the git merge but it results in an ugly Git graph which means that it would be good to make it optional.

Additionally, we could try a fast-forward first followed by an attempt to rebase, followed by a merge or cherry-pick... Which should make it look pretty in git but may not be the most representative so we probably need to add some flags here.

@orao orao added this to the Version 0.5 milestone Apr 6, 2016
@orao orao self-assigned this Apr 6, 2016
@orao orao modified the milestones: Version 0.5, Version 0.6, Future Apr 11, 2016
@orao orao modified the milestones: v0.7, Future Sep 16, 2016
@orao orao modified the milestones: Future, v0.7 Oct 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant