Skip to content

Migrate Sidecar to Ectropy and Plumb - #36

Closed
PerishCode wants to merge 1 commit into
mainfrom
guard/plumb-domain-rollout
Closed

Migrate Sidecar to Ectropy and Plumb#36
PerishCode wants to merge 1 commit into
mainfrom
guard/plumb-domain-rollout

Conversation

@PerishCode

Copy link
Copy Markdown
Owner

Why

Keep the active GitHub mirror aligned with the guarded Forgejo canonical repository.

What

Replace Negentropy with Plumb and Ectropy across repository policy, local guard, and release verification.

Tests

The identical tree passed the complete local guard and Forgejo PR #27.

Replace the retired checker across local guard, Forgejo guard, and release verification. Move repository policy into the canonical ectropy.toml, adopt Sealkit 0.1.8, and keep .runseal as thin operator adapters.
@PerishCode

Copy link
Copy Markdown
Owner Author

Closed after the audited Forgejo landed commit was fast-forwarded directly under the mirror-only ruleset.

@PerishCode PerishCode closed this Jul 28, 2026
@PerishCode
PerishCode deleted the guard/plumb-domain-rollout branch July 28, 2026 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant