tpagectl: visibility updates are record-only, not propagated to Forgejo #559

New issue

Open

opened 2026-08-06 01:03:59 +00:00 by the.auditor · 0 comments

the.auditor commented

2026-08-06 01:03:59 +00:00

Owner

Service.Update in internal/site/service.go persists the visibility field on the site record but does not propagate the change to the backing Forgejo repository. The gitea SDK's EditRepoOption only expresses a binary Private flag and cannot represent limited visibility.

Effect: tpagectl site update SITE --visibility private reports success and shows a before/after diff, while the actual repository access level in Forgejo is unchanged. Users may believe access changed.

Suggested fix: track this limitation as a known gap (e.g. sync private/public binary states where possible, defer limited), or surface a warning when updating visibility that the repo is not re-provisioned.

Ref: PR #558

`Service.Update` in `internal/site/service.go` persists the visibility field on the site record but does not propagate the change to the backing Forgejo repository. The gitea SDK's `EditRepoOption` only expresses a binary `Private` flag and cannot represent `limited` visibility. Effect: `tpagectl site update SITE --visibility private` reports success and shows a before/after diff, while the actual repository access level in Forgejo is unchanged. Users may believe access changed. Suggested fix: track this limitation as a known gap (e.g. sync `private`/`public` binary states where possible, defer `limited`), or surface a warning when updating visibility that the repo is not re-provisioned. Ref: PR #558

the.auditor added the

Kind/Enhancement

Priority

Low

labels

2026-08-06 01:04:05 +00:00