Automating from commandline /closeonend:x not well documented

[GoogleCodeExporter]

On http://tortoisegit.org/docs/tortoisegit/tgit-automation.html (and could not 
find any other resourse also) to explain what the magic number on that command 
actually does.

On TortoiseSVN there was missing an option in my mind. I would like 
/command:pull /path:"path" /closeonend:9 (or so), NOT to close the window on :
1. any erro
2. any file changed

but close if there was no file operation and pull/fetch and all went without 
any new files. (in case of commit if not any filest to commit it would just 
disappear after operation).

If I need to do mass operations like pull on many many repositories I would 
like to see only those that actually have any changes on them, or errors. In 
TortoiseSVN this was not possible and DEV's did not see my point. My point is 
that if you need to sync the changes on lets say 20 repositories at once 
clicking trough the OK buttons on all the windows that does not have any 
changes on them is one dull process. And when you clock away most likely you 
close on one window that had real changes on them and that point it is too late 
and you don't even know which was it and so on. Then you can't do the code 
review of the actual changes.

I use this process mainly on checking many OpenSource component projects that I 
need to see what they do and when they make change that affects my own code and 
so on. Hope someone understand what I am after here. Not to see what I really 
don't need to see and see only what I really need to.

Original issue reported on code.google.com by tommi.prami@gmail.com on 31 Jul 2014 at 5:16

[GoogleCodeExporter]

To verify 

I would like to (in case of pull), have close on end param that would "click" 
the OK button for me on a Pull dialog and the Close if there was no file 
operations for me. So I would not need to see all those "Already up to date" 
messages

Original comment by tommi.prami@gmail.com on 31 Jul 2014 at 5:28

[GoogleCodeExporter]

/closeonend:0 Close manually
/closeonend:1 Auto-close if no further options are available
/closeonend:2 Auto-close if no errors

Related Information here:
http://tortoisegit.org/docs/tortoisegit/tgit-dug-settings.html#tgit-dug-settings
-dialogs2

Original comment by yuelinho...@gmail.com on 31 Jul 2014 at 8:21

[GoogleCodeExporter]

PR: https://github.com/TortoiseGit/TortoiseGit/pull/108

Original comment by yuelinho...@gmail.com on 31 Jul 2014 at 8:31

[GoogleCodeExporter]

Sorry. I miss most part of your report. (Except the first sentence.)

So, you want
1. "Auto-close if already up to date." for CLI parameter /closeonend
2. OK button for there are some "in commits", and
   Close button for "Already up to date".

Original comment by yuelinho...@gmail.com on 31 Jul 2014 at 8:59

[GoogleCodeExporter]

3. Auto-close if nothing to commit

Original comment by yuelinho...@gmail.com on 31 Jul 2014 at 9:22

[GoogleCodeExporter]

@sstrickroth
I have a idea that changing the type of the /closeonend value
from [   1,   2,   3, ... ]
to   [ 0x1, 0x2, 0x4, ... ]

So that multi-conditions of auto-close can be fit and be checked.

Original comment by yuelinho...@gmail.com on 31 Jul 2014 at 9:34

[GoogleCodeExporter]

OK,

I try to be more clear with what I would need...

* CloseOnEnd param
1. that would always "Click OK" for me on Pull-dialog
2. and "Click Close-button" on "Git Command Progress" dialog
  - If Already up-to-date

Similarly on different other processes as well.

Now with closeonend:2 which seems to do something I like to do, will force me 
to click OK on the pull dialog.

Original comment by tommi.prami@gmail.com on 31 Jul 2014 at 10:44

[GoogleCodeExporter]

Why not call git.exe directly?

Original comment by sstrickr...@googlemail.com on 31 Jul 2014 at 12:00

[GoogleCodeExporter]

I like the GUI to see the Changes, and calling GIT directly would not help with 
that. I do that at home now, and I have no idea what changed and not, because 
there is too much text on the console (almost always). and do diffing and so, 
directly. or revision graph...

Original comment by tommi.prami@gmail.com on 31 Jul 2014 at 12:13

[GoogleCodeExporter]

TortoiseGit is calling git.exe right now (we're working on moving to libgit2), 
but as long we're using git.exe we do not want to parse it's textoutput as this 
is error prone (e.g. if git changes something).

Original comment by sstrickr...@googlemail.com on 31 Jul 2014 at 12:19

[GoogleCodeExporter]

That explains it a bit.

Original comment by tommi.prami@gmail.com on 31 Jul 2014 at 12:28

[GoogleCodeExporter]

For clicking on OK on the options dialog: We're also planning a /nogui option 
which directly starts the command.

Original comment by sstrickr...@googlemail.com on 31 Jul 2014 at 12:30

[GoogleCodeExporter]

Original comment by sstrickr...@googlemail.com on 1 Aug 2014 at 7:35

• Changed state: Hold