The command line cannot end a clash of two account names by itself #208

New Issue

2026-11-11T08:44:30Z

james.maes commented

2026-11-11 08:44:30 +00:00

From the review of #205 (Gitea accounts). Planned for 1.2.0 or later.

An older gclo does not see the accounts on another forge and can add a GitHub account with the name of one of them. sync --account, accounts edit and accounts remove then refuse the name (exit 2) instead of acting on the first of the two. The way out is to rename one account in the desktop app. Where only the command line is installed there is no way out short of editing a file.

Possible: let accounts edit and accounts remove take --id (the id is in accounts list --json).

Also from that review, lower: a Delete or RecordSyncResult for an unknown id now fails when a file that has to be put back cannot be written (it used to return).

From the review of #205 (Gitea accounts). Planned for 1.2.0 or later. An older gclo does not see the accounts on another forge and can add a GitHub account with the name of one of them. `sync --account`, `accounts edit` and `accounts remove` then refuse the name (exit 2) instead of acting on the first of the two. The way out is to rename one account in the desktop app. Where only the command line is installed there is no way out short of editing a file. Possible: let `accounts edit` and `accounts remove` take `--id` (the id is in `accounts list --json`). Also from that review, lower: a `Delete` or `RecordSyncResult` for an unknown id now fails when a file that has to be put back cannot be written (it used to return).

james.maes referenced this issue

2026-11-11 08:46:08 +00:00

Gitea organizations and accounts beside GitHub #201

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#208