GoKawiilrickub.com/rick/portal/cmd/ciguest/main.go Orgs, members and repositories — everything you need to work and to keep that work secured.
rickub.com/rick/portal/merge/42/files The familiar files-changed, diffs and inline comments — plus an intent marker on every comment, so it is never ambiguous what blocks a merge and what is a passing remark.
rickub.com/rick/portal/actions/runs/318 GitHub Actions workflows run unchanged, so a migration is a push rather than a rewrite — and the .rickub dialect adds what Actions has no syntax for, like test reports built into the run page.
rickub.com/rick/portal/merge/42 A reviewer you trigger on a merge request: a summary, inline notes where they belong, and a clear verdict. Included on every plan, processed in the EU, never used for training.
~/code/portal # same namespace, same token as your git remote $ docker push rickub.com/rick/portal:1.2.0 1.2.0: digest sha256:9f3a… size 2841 $ helm push portal-1.2.0.tgz oci://rickub.com/rick/charts Pushed: rickub.com/rick/charts/portal:1.2.0 $ oras push rickub.com/rick/portal:1.2.0-sbom sbom.spdx.json Pushed · artifact type application/spdx+json Publish and pull any OCI artifact — container images, Helm charts, SBOMs, WASM — from the same namespace as your code, with one login and one permission model.
~/code/portal $ rickub mr create --title "portal: stabilise diffs" → !42 opened · Athena review requested $ curl -H "Authorization: Bearer $TOKEN" rickub.com/api/v1/repos/rick/portal/merge/42 { "number": 42, "state": "open", "athena": { "issues": 2 } } # MCP: rickub.com/mcp — same token, same permissions Drive everything from the rickub CLI or the token-authenticated JSON API. A hosted MCP endpoint lets your agents open, review and merge — under the same permissions you have.