Set-Token Configure or update the HTTPS published location for token-based login.
Description
Set-Token registers an HTTPS published-location URL for the active project folder. It rejects URLs that embed credentials (like https://token@host/path) and only accepts clean HTTPS URLs, so secrets never end up in published configuration. Use this before Test-Login when first setting up a project against GitHub or GitLab over HTTPS.
Recipes
Recipe 1
EXAMPLE 1
Set-Token -RemoteUrl 'https://github.com/example/repo.git'
Recipe 2
EXAMPLE 2
Set-Token -RemoteUrl 'https://gitlab.com/example/repo.git' -RemoteName origin
Notes
Safety:
- Never paste tokens into the URL itself. Use a credential helper instead.
- After Set-Token, run Test-Login to confirm authentication works.
- Failures point at a log file with the full technical detail.
Parameters
-RemoteUrl required String
The HTTPS URL of the published location. Must start with https:// and must not embed a username, password, or token.
-RemoteName optional String
The name of the published location to configure. Defaults to origin.
-LogPath optional String
Override the directory where the diagnostic log for this run is written. Defaults to %LOCALAPPDATA%\GitEasy\Logs.
-WhatIf optional SwitchParameter
-Confirm optional SwitchParameter
Was this page helpful? Report an issue or suggest an improvement →