internal/workspace/backup.go hardcodes the backup remote URL to https://<token>@github.com/user/<repoName>.git and later reports https://github.com/user/<repoName>. There is no opportunity to specify the actual GitHub owner/org (or branch), so every backup pushes to user/main even though the caller might want org/workspace-backups or use gh to create a repo.
Could we surface the owner/URL as flags (and drop the token from the visible URL) so that workspace backups can push to any GitHub repo while still supporting vaulted token + remote authentication? A small follow-up could be to add cue workspace backup --repo org/cue-backups instead of hardcoding user.
internal/workspace/backup.gohardcodes the backup remote URL tohttps://<token>@github.com/user/<repoName>.gitand later reportshttps://github.com/user/<repoName>. There is no opportunity to specify the actual GitHub owner/org (or branch), so every backup pushes touser/maineven though the caller might wantorg/workspace-backupsor useghto create a repo.Could we surface the owner/URL as flags (and drop the token from the visible URL) so that workspace backups can push to any GitHub repo while still supporting
vaulted token + remoteauthentication? A small follow-up could be to addcue workspace backup --repo org/cue-backupsinstead of hardcodinguser.