Committing and pushing
Committing happens in a workspace. The Changes tab of a chat that runs in a workspace has a commit box: write a message and choose Commit, or use the arrow button beside it (Cmd+Shift+Enter) to commit and push in one step. When the branch has commits the remote doesn’t, a Push button shows how many; when the remote has commits you don’t, Pull does the same. A chat on the project’s main checkout shows its changes read-only, because writes go through a workspace.
Pushing uses plain git push to origin. On a Reliant cloud machine, git gets your GitHub token from Reliant at the moment it needs one, through the connection in Settings → GitHub, and no token is ever stored on the machine. On your own computer, git uses whatever credentials that computer already has for the remote.
Pull requests
Once a workspace’s branch is pushed, the Changes tab offers to open a pull request for it, with a title and description you write. If the branch already has one, the same button opens it on GitHub instead. Creating a pull request, and finding the one a branch already has, use the GitHub CLI (gh) on the chat’s machine. If gh isn’t installed, the button says so and links to cli.github.com. Everything else in the Changes tab works without it.
Installing GitHub CLI
gh auth login and follow the prompts.
Default branch detection
To know what a workspace branches from and what a pull request targets, Reliant works out the repository’s default branch. It readsorigin/HEAD first, which a normal clone sets. If that isn’t set, it asks gh, then git remote show origin, and finally falls back to main or master, whichever exists on the remote.
Related topics
- Worktrees & Workspaces
- GitHub integration, for workflows that act on GitHub
- Processes
- Branching