Authorize ExMCP in the Binjovi write integration #693
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/ex-mcp-write-integration-20260913"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ExMCP builds succeed, but Forgejo rejects every Binjovi status and merge request with HTTP 403 because repository ID 394 is absent from authorized_integ_resource_repo. Add ExMCP to the explicit repository scope and create immutable integration Job generation v27.
Validation: bash tests/binjovi.sh; kustomize build kubernetes/flux/infrastructure/binjovi