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
firsttime [2025/07/27 20:32] – adminfirsttime [2025/08/09 12:34] (current) – admin
Line 2: Line 2:
  
 **Welcome!**\\ **Welcome!**\\
-Nice to see you here. This page can help you get started. The usual question that a person who has just logged-in to //Git Winch// for the first time would be: //Where do I start?// +Nice to see you here. If you reached here after your first login, do not worry: The //Git Winch// application is still running behind this browser window. Click on the icon on the taskbar to return to it, when you finished reading here.
  
-No Worries! Go to the appropriate section below.+This page can help you get started. The usual question that a person who has just logged-in to //Git Winch// for the first time would be: //Where do I start?//  
 + 
 +No Worries! If you are completely unfamiliar with //Git Winch// read the "Concepts" first (Link at the bottom)  
 + 
 +Else, go to the appropriate section below. If you are confused about the terminologies used here, they are explained at the end of this topic.
  
 **If you are the owner of an office (or a division of an office)**\\ **If you are the owner of an office (or a division of an office)**\\
-If you were the one who wants to delegate work to your staff, this is where you start. Firstly, you would need to get an //"orgname"// for you and those who work under you. Then you would need to create a repository. But before that you would need to create an account at either GitLab (preferred) or GitHub or Gitea.+If you were the one who wants to delegate work to your staff, this is where you start. Firstly, you would need to get an //"org code"// for you and those who work under you. Then you would need to create a repository. But before that you would need to create an account at either GitLab (preferred) or GitHub or Gitea.
  
-You can add/remove members to the repositories that you create. You can also delegate someone else to act as a manager. If you want to set the same person as a manager to multiple repositories, you would have to delegate to each repository individually to the same person. Once a person becomes a manager, then that person can add/remove members and even create the repository that the person was delegated to.+You can add/remove members to the repositories that you create. You can also delegate someone else to act as a manager to any/all the repositories of your office.  
 + 
 +If you want to set the same person as a manager to multiple repositories, you would have to delegate to each repository individually to the same person. 
 + 
 +Once a person becomes a manager, then that person can add/remove members and even create the repository that the person was delegated to.
  
 NOTE: We use the term "office" and "division" (of an office) interchangeably. It just means a set of people who work together to advance the entire office -- or that division in the office where you started using //Git Winch.// NOTE: We use the term "office" and "division" (of an office) interchangeably. It just means a set of people who work together to advance the entire office -- or that division in the office where you started using //Git Winch.//
  
 **If you are a manager of an office**\\ **If you are a manager of an office**\\
-You would be a manager, if an owner of an office who started using //Git Winch// would have made you one. So that person would have told you something of this nature: "You have been made a manager for this repository" +You would be a manager, if an owner of an office who started using //Git Winch// would have made you one. So that person would have told you something of this nature: "You have been made a manager for this repository" Not just that... the owner should have given you a file with the the //encrypted PAT.// 
  
 Also that person would have told you the //"orgname"// of that office. Make sure the file orgname.txt containing such //"orgname"// is kept in the same folder as that of the //Git Winch// application. Also that person would have told you the //"orgname"// of that office. Make sure the file orgname.txt containing such //"orgname"// is kept in the same folder as that of the //Git Winch// application.
Line 23: Line 31:
 Some person from your office would have told you the //"orgname"// of that office. Make sure the file orgname.txt containing such //"orgname"// is kept in the same folder as that of the //Git Winch// application. Only then double click on "gitwinch-for-windows.exe" to start running //Git Winch.// Some person from your office would have told you the //"orgname"// of that office. Make sure the file orgname.txt containing such //"orgname"// is kept in the same folder as that of the //Git Winch// application. Only then double click on "gitwinch-for-windows.exe" to start running //Git Winch.//
  
 +
 +**Terminologies**\\
 +  * **Git Host:** A place where the office's Git repositories are centrally stored. We support 3: Gitlab (recommended), Github and Gitea
 +  * **Git:** An application that runs in your computer that interacts with the Git Host
 +  * **Repository:** Kind of a folder -- but a lot more: It even stores various versions of the files in there.
 +  * **PAT:** Personal Access Token. This is obtained by the owner when he/she takes an account at one of the Git Host
 +  * **Encrypted PAT:** An encrypted version of the PAT that the owner can safely give to a manager without the worry that the manager would get ALL access to the Git host.
  
 ----- -----
 [[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]] | [[tos?do=export_xhtml|License and Terms of Service]] [[/concepts?do=export_xhtml | Learn the concepts]] | [[/topics?do=export_xhtml | Table of Contents]] | [[tos?do=export_xhtml|License and Terms of Service]]
  
firsttime.1753641151.txt.gz · Last modified: by admin

Page Tools