officer
9d219e9c8c
Gitea needs allow-same-origin to keep a session and allow-scripts for the interface to work, and those two together give back everything sandbox takes away. The browser says so on every load: "an iframe which has both allow-scripts and allow-same-origin can escape its sandboxing." So it was decoration that emitted a warning nobody can act on, which is how people learn to ignore warnings. What actually stands here is that this is Gitea's own interface, on the platform's own origin, through a proxy the platform wrote.
Gitea
Your own Gitea inside Officer — repositories, issues and pull requests, rendered as the real thing rather than a copy of it.
What you get
Gitea's own web interface, in an Officer panel. Not a reimplementation: the actual application, proxied through Officer so it stays signed in, with an open in a new tab button for anything the frame handles badly.
Requirements
A Gitea instance Officer can reach.
Setup
Install the plugin, open /gitea, and set the instance URL and an API token in the connection panel. Then sign in to Gitea inside the frame, once — the frame shows your Gitea account, not the owner's.
The stored token is used only for the small things around the frame. Everything you see in it is your own session.
For agents
This plugin ships an affordance: use plain git for clone, fetch, pull and push; use tea for pull
requests, issues, comments and releases. tea is logged in as you, with your permissions.
Permissions
One permission, gitea, grantable per role like any other app permission. Each account reaches its own
Gitea identity.