Open PDF files in the Acrobat Reader Desktop App

 Open PDFs in Acrobat Reader from Chrome

Git repo - Hard Reset using TortoiseGit

Important Tip: 

Create a Backup Copy (zip file) of your local repo on your machine then . . .

To perform a hard reset on a Git repository using TortoiseGit, you'll use the "Reset" option from the context menu. 

This action discards all uncommitted changes in your working directory and aligns your branch's state with a specific commit. 

Because a hard reset is a destructive action, it's crucial to be certain you want to permanently discard your changes before proceeding. ⚠️

---

Step-by-Step Guide

1. Right-Click on your Git-controlled folder to bring up the context menu.

2. Navigate to TortoiseGit > Show log.This will open the reset dialog box.

3. Select a Commit in the Repo, then Right Click on Reset "master" to this. . .  

4. In the dialog box, you have two main options to configure the reset:

• "To commit": This field allows you to specify the target commit to which you want to reset your branch. You can either type the commit hash, branch name, or a tag name directly into the box. Alternatively, you can use the ... button to open the log dialog and select the desired commit visually.

• "Reset type": From the Dialog Options select "Hard Reset . . .". This is the key step. Choosing "Hard" will discard all your local changes (staged and unstaged) and move your branch's pointer to the selected commit. 

• The other options, "Soft" and "Mixed," are less destructive and won't be covered here.

• 

• 
  

5. Once you've selected the correct commit and chosen "Hard" as the reset type, click "OK"..

After clicking "Yes," TortoiseGit will execute the hard reset, and your working directory will be reverted to the state of the selected commit. 

All files that were changed or added since that commit will be permanently deleted from your local copy. 

Git Repo Alerts

The latest release (10-Aug-2025) or later of the Parts Frontend application (Parts_Frontend.accde) includes Git Repo Status Alerts.

The purpose of the Git Alerts are two fold. 

1. To remind and prompt users to commit changes staged in their local repositories to the master repository.
   
   
2. To remind and prompt users to Pull Changes from the master repository when their local repo is not in sync with the master repository.

The option to use Git Alerts can be enabled or disabled in the Parts Frontend Config Table or by closing Parts and editing the user.ini file. The user.ini can be found in the same folder as the Parts Frontend.accde file.

If you concerns or questions please Contact Parts

That's it !