Connect GitHub
Sign in to GitHub once to copy your repositories into new projects and let your agents push and open pull requests as you.
Yardmaster uses your GitHub sign-in to copy a repository from GitHub into a new project, and to let your agents push code and open pull requests under your name. You sign in once, through GitHub's own command-line tool, the GitHub CLI.
Sign in and copy a repository#
Click the + at the top of the projects column, then Add Project, and choose GitHub.
If it says Set a default folder to unlock GitHub cloning, click Choose Default Projects Folder and pick the folder your projects go in.
If it says Install GitHub CLI to browse your repos, click GitHub CLI to download it, install it, then close and reopen this window.
Click Connect GitHub. An Authorize GitHub window shows a one-time code, and GitHub opens in your web browser.
Click Copy code, paste it on the GitHub page and approve. The window closes by itself when GitHub confirms.
Pick the account or organization, find the repository with Filter repos... and click it.
Click Clone & Create Project.
You can also paste a link into Repository URL (or type it short, like owner/repo) without signing in, for a public repository. The copy lands in your Default Projects Folder; see Projects.
Closing the Authorize GitHub window cancels the sign-in.
What your agents can do with it#
The sign-in itself stays with the GitHub CLI on this computer. Yardmaster asks the GitHub CLI for it when needed and keeps a copy in memory only, checking it again about every 30 seconds. Nothing is sent to Yardmaster's servers.
Switch GitHub accounts#
If you change accounts in the GitHub CLI and a session still acts as the old one, open Settings > Diagnostics and click Refresh GitHub auth. The next session you start picks up the new account.
To disconnect GitHub completely, sign out of the GitHub CLI (gh auth logout in a terminal).
Where did the Pull Requests and Issues tabs go?#
The built-in GitHub, Pull Requests, GitHub Issues, Code Search and GitHub Releases sidebar entries were removed. Pull requests and issues now come from:
Reviewer, for pull requests you write or review; see Reviewer.
PR Merge Queue, for seeing and merging your open pull requests; see Work with pull requests. A GitHub plugin was planned for the Marketplace, but the Marketplace has no plugins today, so issues are read on github.com.
What the sign-in asks for. Connecting runs the GitHub CLI's sign-in with the extra notifications permission. The GitHub CLI's usual sign-in also covers your repositories, so treat it like any app with access to your code.
Several accounts. When the GitHub CLI holds more than one account, the account picker in step 5 lists them, and an agent gets the first account that can reach the repository.
Signing in to Yardmaster with GitHub is a different thing: it is one way to sign in to your Yardmaster account; see Your account.
Related
- Merge pull requests with PR Merge QueueSee your open GitHub pull requests sorted by how ready they are, have an agent get one ready to merge, and merge, review or close it from its card.
- Add and organize your projectsA project is a folder on your computer that your agents work in. Add one, group them, and change a project when its folder moves.
- Review pull requests with ReviewerFor people who review code on GitHub: Reviewer lists your pull requests and review requests, drafts a review with AI when you ask, and posts only when you click.