Repositories
Add a repository
rness add api # a repository of your organization
rness add acme/api # any owner
rness add https://github.com/acme/api.git # any URLadd clones the repository under org/ (or adopts a clone already there) and declares it in rness.json for the whole team. Commit rness.json in .rness. A blank workspace has no organization, so there give <owner>/<repo> or a URL.
A monorepo is a repository like any other. Its parts become scopes, each with its own context:
rness add platform --scopes apps/web,packages/uiClone what your teammates added
rness sync offers, in a terminal, to clone the repositories of rness.json you do not have yet.
rness sync --all # clone every repository of the list
rness sync --pull # pull every clean clone firstPrivate repositories
Without a login, Rness lists public repositories only. To reach the private ones:
rness loginRness shows a code and https://github.com/login/device. Approve the code in a browser, on any machine. The login is stored in ~/.config/rness/auth.json (%APPDATA% on Windows), readable by you only, and renews itself. rness logout forgets it.
- Rness asks for the
repoandread:orgscopes. GitHub has no read-only scope for private repositories, but Rness only lists and clones them. Where the workspace uses Agent Pulse, it also asks forproject, to write the board. - An organization that restricts OAuth apps hides its private repositories until an owner approves "Rness".
rness createsays so, with the link. - In CI, set
GITHUB_TOKENorGH_TOKEN. Either one takes precedence over the login.
SSH or HTTPS
create and add test your SSH access to github.com once. They write git@github.com: URLs when GitHub accepts your key, and https://github.com/ URLs otherwise. --ssh and --https choose without the test.
Over HTTPS, Rness's own clones and pulls use your login. For your own git pull and git push, rness login offers to act as git's credential helper for github.com (rness login --setup-git); rness logout undoes it.