Jump to content

Rhys

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Rhys

  • Rank
    Newbie
  1. Thanks for the clarification, Carlos. I am still a bit confused as to how the operation would be different to a stash > switch changesets > unstash approach, but I might be missing something in that article. Stashing itself would also be convenient, but from my understanding our Cloud account does not provide this, though I may be mistaken. For the purposes of not committing this in-progress project state, "checkin changes to a different branch" doesn't seem to fit to bill too well for this scenario for us.
  2. When a workspace has pending changes and the branch it is on has newer commits, the GUI provides the View New Changes button, allowing the changes to persist and resolve against the changes made. This is useful, as it doesn't require a new changeset to be created and local changes are retained. Does such functionality exist for branch switching? Often in our workflow, there are a common set of changes that can occur locally that prevent us from discarding if we want to switch to a neighbouring branch. It seems that such a workspace change would follow the similar process of resolving the changes without necessitating a commit, is that correct? Possibly a command line option could resolve this outside of the GUI also.
×
×
  • Create New...