Computers, terminal and Git

GitHub

The optional github plugin connects your own GitHub account and maps a Project to its repository, so your terminal commands in that Project run as you.

The plugin adds no tools. Chetty works with GitHub through git and the GitHub CLI (gh) in the terminal, and the mapping holder's commands are signed in as the holder. For the complete Project workflow, see Projects overview.

Install the plugin

Open Settings → Available plugins and install github.

Then connect your GitHub account, as described below. Check the registry for the plugin's current version and minimum Chetty version. This plugin supports Linux only; Windows and macOS are not supported.

Connect your GitHub account

Open Account → Linked accounts.
Select Connect GitHub. Chetty shows a one-time code.
Open the GitHub verification page, enter the code and approve the request.

The GitHub row then shows the connected login, Test connection, Replace identity and Disconnect. When the authorization has lapsed, it offers Reconnect instead.

There is no personal access token field: Chetty uses the GitHub CLI device login with the workflow scope, so gh must be installed on the Chetty host.

Note: Chetty does not refresh the authorization silently. When GitHub asks for a reconnection, connect again.

Only one connection request runs per account at a time. Reloading the account panel resumes its pending code.

Map a Project to its repository

Open the Project and its GitHub tab.
Fill in Base repository and Push repository. The form suggests repositories from the Project's Git remotes, and an unmapped Project lists the repositories its remotes name. There is no Detect button.
Select Save mapping. Chetty checks that your GitHub account can read the base repository and push to the push repository.

The two repositories may differ, which is what a fork workflow needs.

A Project has at most one mapping, held by the account that created it. Another account cannot map a Project that is already mapped, and only the holder or an administrator can remove the mapping. Other members of a shared Project see that it is mapped and by whom.

Deleting a Project removes its mapping and pending mapping confirmations. Your GitHub connection, your repositories and the mappings of other Projects stay.

Note: A paired computer cannot be mapped. It runs git and gh with its own sign-in, so its GitHub tab says so instead of offering a mapping.

Git and gh in the terminal

When the mapping holder runs a terminal command in the mapped Project, Chetty supplies the holder's GitHub token to that command only. git over HTTPS and gh then work without storing a credential in the home directory.

Publishing a branch, opening a pull request, reviewing and merging are ordinary git and gh commands. The plugin adds no tools or buttons for them.

Commands of other accounts, and commands in a Project without a verified mapping, run without a GitHub identity. Managed Project environments created from the current image include gh; an environment created from an older image may need it installed separately.

Warning: A managed container is shared and runs as root, so another member can inspect your token in a running process. Treat a mapping on a shared Project as visible to its members.

Disconnecting GitHub or removing the mapping stops future commands from receiving the token. A command that has already received it keeps it until it ends.

Connection lifecycle

Disconnecting cancels a pending login and deactivates repository mappings. Reconnecting verifies the existing mappings before enabling them again. A cancellation, account deletion or mapping edit during that verification cannot restore outdated state.

Cancelling or letting the code expire clears it. A daemon restart or plugin reload interrupts the request, so you log in again.

Disconnecting, replacing the GitHub identity and removing a mapping each show a confirmation first.

Note: A confirmation works once and expires after five minutes. If the account or mapping changes in the meantime, preview the action again.

Accounts and permissions

The plugin has no settings of its own and no per-account grant. The GitHub row belongs to the signed-in account, and Project membership decides who sees a mapping. For accounts and permissions in general, see Users and access overview.