This code is always needed for Git Winch to work fully. It represents the organization …(or it can even be a division in an organization.) We call this the “orgname” in these docs.

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 situation, 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.

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 can request this file from the owner/manager of the office you work for, and copy it into the application folder of Git Winch.

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

Git Winch cannot work without the orgname. So when you start the application, if it is found that the orgname is NOT available, it will ask you to select or set one. If you plan to create an orgname for yourself, then give 'own' for the full name of the owner of that orgname.

Why?
The orgname is needed as a kind of 'category' or 'set' into which all your repositories would be connected to. You are free to create as many orgname that you may need to organize your office work. It would be the owner of an office who would usually set an orgname. You can choose any name you want (See restrictions below) Others who work along with you on the same repositories would also have to use the same orgname.

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 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 different orgname 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