Once I started the push, I might want to switch to a different branch. It'll be nice if SmartGit had some kind of command queue, so I could do another command while a command is already taking place, and then it'll get executed automatically when the first command is done.įor example, I could be pushing to a remote repo, which might take 5 seconds. It means that when I'm working with SmartGit, I spend a lot of my time twiddling my thumbs waiting for it to do one action before I issue the next one, and computers aren't supposed to be like this. One of the frustrating things when you're working with SmartGit is that every time you're doing an action (like fetch or commit or cherry-pick) you can't do almost anything with the interface until it completes. This is a complex and difficult feature that I've wanted for many years, and have bugged the SmartGit team about several times. Right clicking on an unticked tag would operate on that tag alone.ĥ) Expand the right click menu on a branch in the Branches pane to include Push Tags/Push Tags To. there should allow multiple upstream repos to be selectedĤ) Group operations in the Tags list - allow pushing of several tags by right click on one of a group that are ticked. should allow more than one selectionģ) Right click on an individual tag - the Push To. Actually it might be eight operations - I didn't check last time whether a ticked tag forms part of a selection and the whole selection is operated on or only the right-clicked tag.ġ) Right click on the Tags section of the Branches pane and have new options Push All to All Upstream and Push All To.Ģ) Push All To. both of which only allow one upstream to be selected at a time, meaning that I have to locate and tick each of the two new tags and then do four Push/Push To operations to get the tags into all of the upstream repos. In Smartgit the operations on tags currently are Push and Push To. As far as I can see, SmartGit only allows one tag to be pushed to one remote at a time. This is easy at the git shell level with git push -tags however it's one of the few occasions where SmartGit doesn't provide a better way of doing it.
To mark a release I put a tag on two branches (we release two variants each time) and then need to send it upstream to all the repos so that they have it. The Release repo and its fork are updated each time a release is made. The Master repo and its fork are where we work. One local repo encapsulating four similar upstream repos (master repo, fork of master repo, release repo, fork of release repo) containing the same code.
0 kommentar(er)
