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
definitions [2025/07/09 18:26] – admindefinitions [2025/08/05 18:16] (current) – admin
Line 1: Line 1:
 ======Definitions====== ======Definitions======
  
-**What is a //repository//?**\\+**What is a //repository//?** (also called "repo" or "repos") \\
 Simply speaking, think of a repository as a folder inside which files and sub-folders are stored. But it is actually more than that: It also stores earlier versions of the files in there too.  Simply speaking, think of a repository as a folder inside which files and sub-folders are stored. But it is actually more than that: It also stores earlier versions of the files in there too. 
  
 The repository is centrally stored at the Git Host you have an account with. All members allowed to work on a repository will have a //working copy// of that repository on their own respective computers. //Git Winch// has useful functions so that all those members have the correct files from that central Git Host. The repository is centrally stored at the Git Host you have an account with. All members allowed to work on a repository will have a //working copy// of that repository on their own respective computers. //Git Winch// has useful functions so that all those members have the correct files from that central Git Host.
  
-When you use //Git Winch// usually you would create more than one repository -- each one created to ensure that the members working on the files therein only handle just those files they need to work on, and not others. So the work of an office can be separated on a //need-to-know// basis. In case someone leaves the office, that person does not get the //entire// data of the office (which often would have been the case if the office did not use //Git Winch!//)+Offices using //Git Winch// usually will create more than one repository -- each one created to ensure that the members working on the files therein only handle just those files they need to work on, and not others. So the work of an office can be separated on a //need-to-know// basis. In case someone leaves the office, that person does not get the //entire// data of the office (which often would have been the case if the office did not use //Git Winch!//)
  
-**What is an //org// or //orgname//?**\\ +**What is an //org// and //org code//?**\\ 
-In //Git Winch// repositories are assumed to belong to some organization (or a division in the organization) We use the term: //orgname// to represent a short code that represents such an organization (or division). Not much work can be done if an //orgname// is not set when you start //Git Winch// If set correctly, the //orgname// can be seen at the bottom left corner of //Git Winch.// Press F1 when the mouse is hovering there to learn more.+In //Git Winch// repositories are assumed to belong to some organization (or a division in the organization) That is what we mean by an "org".  
 + 
 +//Org code// represent a short code that represents such an organization (or division). Not much work can be done if an //orgname// is not set when you start //Git Winch.// If set correctly, the //orgname// can be seen at the bottom left corner of //Git Winch.// Press F1 when the mouse is hovering there to learn more. 
 + 
 +//Orgname// can ONLY be set by a main, responsible person (usually the owner) of the office. Such a person can delegate other work to managers in case the owner himself/herself does not have time.
  
  
definitions.1752078383.txt.gz · Last modified: by admin

Page Tools