Soho Posted May 18, 2012 Report Share Posted May 18, 2012 When I am working distributed I am often without connection to our issue tracker. This means that I have to use a temporary naming scheme for new branches. When I later sync with the main repository I may not have created the issues in the tracker yet. When I do, I have to rename all branches in all replications which is easily forgotten, thus leaving the different replications with differently named branches. Obviously this is a mess, so it would be really nice, if Plastic synchronized branch name changes. If there is a rename conflict, I would be fine if the newest name was chosen or better if the user could choose. Link to comment Share on other sites More sharing options...
manu Posted May 18, 2012 Report Share Posted May 18, 2012 Can you please add the suggestion into the user voice system? Thanks! Link to comment Share on other sites More sharing options...
psantosl Posted May 26, 2012 Report Share Posted May 26, 2012 Yes, well, the problem is that it is not so easy. Sometimes users replicate a branch and want to give it a different name for whatever project reasons. Changing the name of the source repo when you push your changes back is simply not an option. We could add checks or permissions to it, but it does sound a little bit overloaded for an operation which shouldn't happen very often. We can all rename branches but it is not the most usual function. We'll study the proposal, sure, and try to figure out the best way to implement it. Thanks!! Link to comment Share on other sites More sharing options...
Soho Posted May 29, 2012 Author Report Share Posted May 29, 2012 If synchronizing branch names will disturb some peoples workflow, then you could make it optional or provide an explicit button for it. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.