TGit | Control TortoiseGit from within Visual Studio | Code Editor library

I have this code in my $profile in PS version 5:

I am looking for the equivalent of git log --pretty=fuller in Tortoise git. https://tortoisegit.org/docs/tortoisegit/tgit-dug-showlog.html for example consistently just says "date" while there are two dates -- and Tortoise Git actually allows you to alter one of them.

I'm using TortoiseGit 2.8.0.0 with Git 2.20.1.windows.1 on Windows 10. In TGit I specified a start_commit_hook to execute a .bat file from the home folder of the local repository.

According to TortoiseGit Manual:

Start-commit: Called before the commit dialog is shown. You might want to use this if the hook modifies a versioned file and affects the list of files that need to be committed and/or commit message. However you should note that because the hook is called at an early stage, the full list of objects selected for commit is not available.

And indeed that's what I want: The hook shall modify some files before they are committed, while this is not regarding the commit message.

Problem: The hook script is executed later than expected. This happens after the commit has been executed, which causes the files to be changed after the commit is finished.

Did I miss anything to configure?

How do you set the default dates range in TortoiseGit log dialog?

In the Filtering Log Messages of the TortoiseGit Manual it is mentioned that:

A default limitation for From can be configured in the settings dialog on the Dialogs 1 page (cf. the section called “TortoiseGit Dialog Settings”).

But on TortoiseGit 2.4.0.2, in that dialog I cannot find such a possibility.

I am having a problem passing parameters to an external bash script file from git aliases. Currently, I have my bash script file in the same directory as my .gitconfig. I plan on moving all my complex !f() { } aliases in there to avoid battling all the escaping and no commenting.

So my script file is named .gitconfig.kat.aliases.script and it looks something like this:

I want to download and verify TortoiseGit-2.8.0.0-64bit.msi

I use gnupg2 (in Cygwin)

The TortoiseGit download page provides these files:

My question is strictly related to this one: I have Tortoise Git and I need to temporary switch to a previous state where I placed a tag, then make a modification of that version and after rollback to the current state, losing the modification made (so I want to go back to the initial state).

Since I cannot mess up with the code, is the procedure explained in the related question sufficient? Should I select the option "Create a new branch" when I switch back or not? If I don't, later on can I just use:

• Explorer -> Switch/Checkout
• Select branch
• master OK

to come back to the initial state?

EDIT For instance what happen if in this window I switch to a certain tag without selecting the option to create a new branch? Would I be able to switch to the master initial state again?

I have a folder with files in my woring directory, not yet under version control. If I right click on the folder and go to TortoiseGit -> Add I get the message:

There is nothing to add. All the files and folders are either under version control, have been ignored or the global ignore configuration setting.

When I go into the folder and select the individual files I can add them. And if I start a command line and use git add --all it does what I want TortoiseGit to do and adds recursively.

According to the TortoiseGit Manual it should be able to do this:

Many Adds: You can also use the Add command on folders. In that case, the add dialog will show you all unversioned files inside that versioned folder. This helps if you have many new files and need to add them all at once.

What am I missing?

I just wrote a script to release a build of one of the products I'm working on. The script does the job, but I don't really like the code itself, looks like spaghetti code and callback hell combined.

Is there a cleaner way to do this? I'd like to be able to run commands in series, log the outputs (stdout.on('data')) and when the task is finished. (easier for further debug and when waiting for the task to be done, reassuring to know what's happening on the background)

Maybe using Promises would help clean the mess a bit, but still, I feel like there should be a cleaner way to deal with multiple commands.

Some explanation about what the code does:

1. Create a tag with the commit you want and the tag version you want, i.e: git tag 1.2.5.
2. Build the release file with gulp build.
3. Create a folder doc/.
4. Convert doc/doc_reader.odt to doc//documentation.pdf. (Open it and export as PDF)
5. Copy build/reader.js and doc/changelog.txt in the created folder.
6. Zip the 3 files.
7. Commit everything with commit message: Release 1.2.11 (for example)
8. Push.
9. Create a new release on GitHub using the commit you just pushed and the same tag.

Here is the code, as an example. (ES5, Node 4.6.0+)