This code is always needed for Git Winch to work fully. It represents the organization …or the division in the organization. If you cannot see anything here (i.e. it is blank) it means that currently this Org/Div name was not found as the application started. Usually, that happens when running a fresh installation of Git Winch for the first time. In such a situations, some of the activities cannot be done as Git Winch will not know which organization to work with. So you would get prompted to set this value as soon as possible.

We call this the “orgname” in these docs.

This “orgname” is set using the text stored in a special file named orgname.txt in the same folder where the application was installed. The contents of this file is used as this code. This file is NOT bundled in the installation zip file. If you are working for someone else, you would get this file from the owner/manager of the office you work for, and copy it into the application folder.

If set correctly, this code will be seen at the bottom left corner of the Git Winch Client Application.

Owner can create the orgname.txt
If you are the owner yourself, then you can create this orgname by attempting to create your first repository in the Manage page of Git Winch. Click the [+] button there and Git Winch will check if the orgname is given or not. If not, it will then ask you to create it first. Before creating, enter the owners PAT token in the PAT input-box. It will ask you for the orgname you want to use. The server will check if that was booked by someone else, in which case you will be asked to do this process again.

Manager can also create the orgname.txt
If you have been assigned as a manager of a repository by the owner, then you should NOT enter the owner's PAT token (as you would not have that) Leave it empty and it will ask you for the encrypted version of the PAT token that the owner had given you. And proceed as above.

Once you; either as the owner or the manager, had created the orgname, you will be able to see the orgname.txt in the application folder. Copy that and give it to your office workers so that they can save in their respective application folders.

NOTE: orgname can only have alphanumeric characters and optionally, you can also use underscores. A minimum of 4 characters is needed. If the file contains more than 8 characters, the rest would be ignored.

What orgname to use?
As an owner, you can choose whatever name you want, as long as it is as per the specs given here… and someone else must not have claimed it. Once you get the orgname you must communicate this name to other team members. Best way to do that is simply share the file “orgname.txt” to them. And ask them to save that file in the application's folder.

Changing this Org or Division Code
Usually, you would use only ONE orgname code and use that always. But in some offices, the same person may be working in two different divisions. In that case, that person may want to change this orgname, to switch to the correct organization/division.

You can change the organization code when working inside the application: Double click on the orgname at the bottm left corner, and it will prompt you for the new orgname.

IMPORTANT
If you work on a repository which is from a differentorgname then it will give a warning and/or work incorrectly.

Why?
Git Winch is used by many organizations. Some of them may have multiple divisions in them. This is used to differentiate between them. Also, it reduces the chance of “clashes” for the repository names that you use; as our coordination server may be handling the metadata for thousands of repositories.

Learn the concepts | Table of Contents