Git Winch Guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
advancednotes [2025/05/05 10:58] – cherinadvancednotes [2025/05/12 16:27] (current) – [🛠️ How to Set Up External Git Tools] cherin
Line 1: Line 1:
-====== Advanced Notes ====== +====== Using TortoiseGit / Git command line======
-===== Using TortoiseGit / Git Bash / Command Prompt for Git Operations =====+
  
 ==== 🧭 What is this about? ==== ==== 🧭 What is this about? ====
-While **GitWinch** is designed to simplify collaboration by managing Git repositories, locking files, and notifying users of changes, some advanced users may prefer to use **Git Bash**, **Command Prompt**, or **TortoiseGit** for operations beyond the GitWinch scope — such as merging branches, resolving conflicts manually, viewing logs, or advanced history manipulation.+While **Git Winch** is designed to simplify collaboration by managing Git repositories, locking files, and notifying users of changes, some advanced users may prefer to use **Git Bash**, **Command Prompt**, or **TortoiseGit** for operations beyond the Git Winch scope — such as creating branches, merging branches, resolving conflicts manually, viewing logs, or advanced history manipulation.
  
 ==== ⏰ When would I need this? ==== ==== ⏰ When would I need this? ====
-You may need this setup **after cloning a repository using GitWinch**, if:+You may need this setup **after cloning a repository using Git Winch**, if:
   * You want to do more than just `clone`, `add`, `commit`, `push`, and `pull`   * You want to do more than just `clone`, `add`, `commit`, `push`, and `pull`
   * You prefer visual tools like **TortoiseGit** or want full control with **Git Bash**   * You prefer visual tools like **TortoiseGit** or want full control with **Git Bash**
-  * You encounter a situation GitWinch doesn't handle (e.g. resolving a conflict manually)+  * You encounter a situation Git Winch doesn't handle (e.g. resolving a conflict manually)
  
 ==== ❓ Why use other Git tools? ==== ==== ❓ Why use other Git tools? ====
-While GitWinch is designed to handle typical collaboration tasks and prevent file conflicts via its locking mechanism, it intentionally avoids exposing the full Git command set to avoid confusion for non-technical users.+While Git Winch is designed to handle typical collaboration tasks and prevent file conflicts via its locking mechanism, it intentionally avoids exposing the full Git command set to avoid confusion for non-technical users.
  
 Advanced users may want: Advanced users may want:
Line 20: Line 19:
   * Integration with other Git-based workflows   * Integration with other Git-based workflows
  
-This guide enables you to extend GitWinch repositories into your preferred Git environment without breaking access controls.+This guide enables you to extend Git Winch repositories into your preferred Git environment without breaking access controls.
  
 ==== 🗂️ Where does this apply? ==== ==== 🗂️ Where does this apply? ====
-This setup applies to **each Git repository** cloned by GitWinch, regardless of whether it's hosted on GitHub, GitLab, or Gitea. It needs to be configured **once per repository**, and works on any system where OpenSSH is available (e.g., Windows 10/11 with Git and TortoiseGit installed).+This setup applies to **each Git repository** cloned by Git Winch, regardless of whether it's hosted on GitHub, GitLab, or Gitea. It needs to be configured **once per repository**, and works on any system where OpenSSH is available (e.g., Windows 10/11 with Git and TortoiseGit installed).
 --- ---
 ==== 🛠️ How to Set Up External Git Tools ==== ==== 🛠️ How to Set Up External Git Tools ====
Line 29: Line 28:
 === Step 1: Configure SSH Access for Git CLI === === Step 1: Configure SSH Access for Git CLI ===
  
-After cloning a repository with GitWinch, run the following command to link the correct `.priv` key (used for deploy access) with that specific repo:+After cloning a repository with Git Winch, run the following command to link the correct `.priv` key (used for deploy access) with that specific repo:
  
   git -C "<path-to-repo>\<repo-name>" config core.sshCommand "ssh -i \"<path-to-key>/<repo>_<member>.priv\" -o IdentitiesOnly=yes"   git -C "<path-to-repo>\<repo-name>" config core.sshCommand "ssh -i \"<path-to-key>/<repo>_<member>.priv\" -o IdentitiesOnly=yes"
Line 40: Line 39:
 This command writes the key configuration into the repository’s `.git/config` file, making it persistent and repo-specific. This command writes the key configuration into the repository’s `.git/config` file, making it persistent and repo-specific.
  
----+----
  
 === Step 2: Configure TortoiseGit to Use OpenSSH === === Step 2: Configure TortoiseGit to Use OpenSSH ===
Line 52: Line 51:
  
 This enables TortoiseGit to invoke the same SSH client used by Git CLI and honor the `core.sshCommand` setting stored in the repo. This enables TortoiseGit to invoke the same SSH client used by Git CLI and honor the `core.sshCommand` setting stored in the repo.
---- +---- 
-🎯 With this setup, you can use TortoiseGit, Git Bash, or the Command Prompt seamlessly alongside GitWinch, without needing Pageant or modifying your global `.ssh/config`. Each repo remains isolated with its own deploy key and member access — exactly as GitWinch intends.+🎯 With this setup, you can use TortoiseGit, Git Bash, or the Command Prompt seamlessly alongside Git Winch, without needing Pageant or modifying your global `.ssh/config`. Each repo remains isolated with its own deploy key and member access — exactly as Git Winch intends. 
 + 
 + 
 +---- 
 +[[advanced?do=export_xhtml|Advanced uses]] | [[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]] 
 +   
  
  
advancednotes.1746435503.txt.gz · Last modified: by cherin

Page Tools