This is an old revision of the document!
Create a PAT at the Git service where you have an account. It must have permission to create Webhooks along with the ability to create repositories and add Deploy Keys. Enter the PAT in the box at the Manage page, to list repositories, create new ones, and add/remove members.
Currently, Git Winch can work with accounts at GitLab, GitHub, Gitea. You can also self-host Gitlab and Gitea on your own server. Just make sure that the file config.txt and the file .ini file has the correct settings.
In config.txt you need to change the right side after the equals-to “=” to point to the correct URL relevant to the hosting server.
And in the .ini file you must make sure that the GitSys= must be given one of the 3 values: Github or Gitea or Gitlab
Encrypted Version of this PAT
Sometimes, an owner may not want to do all the work of creating of a repository and adding/removing members of a repository from within Git Winch itself. But instead, the owner may decide to make someone else the manager and make that manager do all that work.
The problem now is that if the manager is given this PAT directly, that would be a security risk for the owner: The said manager can get free access to the entire Git Host of the owner. Also, the manager may end up sharing that key to someone else who can wreak havoc.
In short: You should NEVER EVER share the PAT itself with anyone!
We have a solution on how to delegate work to manager:
Right click on this PAT edit box (once you as an owner has written the PAT in there). Git Winch will now encrypt that PAT for you.
You would be asked for the username of the manager you want to delegate work to. The PAT would be encrypted specifically for that manager only and copied to the clipboard.
Then you (again, assuming you are the owner) can send that encrypted PAT to the manager. The manager, now can use that encrypted key to do the work on behalf of the owner, from inside Git Winch. The owner is assured that the PAT is reasonably protected and there are now lesser chances that the owner's Git host will be misused.
Read more how the manager uses this encrypted PAT here