This is a critical code which is always needed for Git Winch to work.
If set correctly, this code can be seen at the bottom left corner of the Git Winch Client Application represents the organization …or the division in the organization.
We call this the “orgname”.
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.
You can easily create/edit this file using text editors such as Notepad, Notepad++, VSCode, etc. (Do NOT use word processors like Microsoft Word, etc.)
NOTE: It 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?
You can choose whatever name you want, as long as it is as per the specs given here. And 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.
The recommended way to change the organization code is to change the contents of the file orgname.txt present in the application folder. When you start Git Winch it is this file which sets the initial orgname.
You can also 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.