You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For people working on multiple things at the same time within the same project it would be a big benefit to see which instance of the cloned repo is pointed at which branch.
Ideal experience would also have the information about whether it's dirty or not.
Personally I tend to have 3+ clones of the same repository I rotate for different work (e.g. I have one longer going thing and then bunch of smaller bug fixes and or features and then a clone for helping people I can safely nuke any and all changes on anytime).
Thank you.
The text was updated successfully, but these errors were encountered:
it would be a big benefit to see which instance of the cloned repo is pointed at which branch.
Seems reasonable, but how many people have a bunch of copies of the same repo?
The thing is, the workflow just parses a bunch of filepaths when updating its list of repos. Calling git or parsing config files would make the refresh way slower. Especially getting dirty status.
So I think that any such feature would have to be optional.
For people working on multiple things at the same time within the same project it would be a big benefit to see which instance of the cloned repo is pointed at which branch.
Ideal experience would also have the information about whether it's dirty or not.
Personally I tend to have 3+ clones of the same repository I rotate for different work (e.g. I have one longer going thing and then bunch of smaller bug fixes and or features and then a clone for helping people I can safely nuke any and all changes on anytime).
Thank you.
The text was updated successfully, but these errors were encountered: