Chapter 12: The GitHub Workbench, place by place

What this chapter covers

The GitHub Workbench is one window for everything GitHub: what needs you, your repositories, searches, people, gists, projects and watches. The other chapters are about jobs, such as reviewing a pull request. This one is about the window itself, so you can find any place in it and know what is there.

It walks through the tree the way it is laid out, one place at a time, starting with Start Here. Then it covers what you can do to a selected row, the help keys, Dry Run, the practice repository and Workbench Options.

By the end you will know where each thing lives, how to get there in one key, and how to ask the window what you can do wherever you are.

Every later section assumes three things, so here they are first.

Opening it

In either editor, turn on View > GitHub Workbench Mode (Alt+V, then K), and the GitHub menu (Alt+G) has the doors in: the Workbench itself, Inbox, this repository’s issues, its pull requests and its Actions runs. Each door opens the window at that place. If the window is already open, the door brings it forward instead of opening a second one. Chapter 1 has the other ways in.

The Workbench is a window of its own, not a dialog. The editor stays usable while it is open, and Alt+Tab moves between them. A smaller window the Workbench opens, such as a run’s logs, blocks only the Workbench, never the editor. Inside the Workbench, Ctrl+Shift+E brings back the editor that opened it. Alt+F4 closes the Workbench; Escape never does. Escape clears the filter box first, and then goes back to where you were. In Details, it returns you to the list instead.

The window remembers where you were for each account: its size and how wide the tree is, the place you had selected, the branches of the tree you had open, and the repositories you visited. Next time it opens there, unless you have chosen Inbox or Start Here in Workbench Options. When you come back to a list, the row you were on is selected again.

Start Here

The first place in the tree, and the place the window opens until you have signed in. Its details pane says what the window is, whether you are signed in, and the five keys to learn first: F6, Enter, Shift+F1, Alt+Enter and Backspace. Ctrl+9 comes back here from anywhere.

Needs My Attention

Everything waiting on you, across GitHub. Ctrl+1 goes straight to Inbox, the first place under it.

When one of these is empty, the details pane says so and says what would fill it, so an empty list never leaves you wondering whether it loaded. Chapter 3 covers working through them.

Repositories

The repository you are working in comes first, then Pinned, Favorites, your own repositories, Starred, Star Lists, Watched, My Packages, My Codespaces and your organizations. Three of GitHub’s own lists, read only, are here too: Licences, .gitignore Templates and Codes of Conduct, the choices a new repository offers.

Ctrl+2 goes to the repository you are working in. Ctrl+L opens any other one: type owner/name, or paste a link, and it gets a place of its own here.

Every repository has the same places under it, in the same order, so once you know one you know them all: Overview, Issues, Pull Requests, Issues and Pull Requests, Discussions, Merge Queue, Actions, Code, Releases, Labels, Milestones, Templates, Projects, Activity, People, Insights, Deployments and Environments, Wiki, GitHub Pages, Security and Settings. Ctrl+Shift+1 to Ctrl+Shift+0 jump to ten of them:

Key Place
Ctrl+Shift+1 Issues
Ctrl+Shift+2 Pull Requests
Ctrl+Shift+3 Discussions
Ctrl+Shift+4 Actions, on its Runs
Ctrl+Shift+5 Code, on its Files
Ctrl+Shift+6 Releases
Ctrl+Shift+7 The repository’s Projects
Ctrl+Shift+8 Security
Ctrl+Shift+9 Settings
Ctrl+Shift+0 Insights

A few things worth knowing:

Ctrl+N makes something new where you are: an issue in Issues, a pull request in Pull Requests, a gist in My Gists, a saved search under Saved Searches, a pin under Pinned, a watch under Watches, and a repository set under Repository Sets. Ctrl+Shift+N asks what to make.

A new issue, and issue forms

Ctrl+N in Issues reads the repository’s issue templates first, then asks which to start from: Blank issue, or one of the templates, each with its own description. That list includes GitHub’s issue forms, the ones written in YAML that show as a form with boxes on the website. Choose one and QUILL fills it as a real form:

If a repository has a form QUILL cannot fill, it says so once and leaves that one off the list; it is still there on GitHub, and Blank issue and the other templates are still offered.

A new pull request

Ctrl+N in Pull Requests opens New Pull Request. To start from a particular branch, select it in Branches and press Ctrl+Shift+N, then choose Pull Request.

If the two branches are the same, or Merge from has nothing that Merge into does not already have, QUILL says so instead of opening the window. If the branch already has an open pull request into the same branch, you are taken to that one rather than making a second, and your text is kept. Cancel keeps what you typed too, for the rest of the session: open New Pull Request on the same two branches and it is waiting for you.

Comparing branches

On a branch, Compare Branches… (Ctrl+Shift+B) shows what one branch has that the other does not, on two tabs: Commits and Changed Files. Commits are newest first. GitHub gives at most 250 commits for one comparison, so when there are more the tab says so, for example “Commits (250 of 1,204, newest)”, and you know you are reading the most recent ones, not all of them. Compare With Default (Ctrl+B) compares the selected branch, tag, release or commit with the default branch, and Compare With Previous (Alt+Shift+B) compares a tag or release with the one before it, or a commit with its parent.

Templates and community files

A repository’s Templates place lists everything GitHub reads to shape new issues, pull requests and discussions: issue forms, Markdown issue templates, the template chooser, pull request templates, discussion forms, and the community files (code of conduct, contributing guide, security policy, support, governance, funding, citation and code owners). Each row says whether the file is the repository’s own, inherited from the organization’s .github repository, or missing.

Three community files have a window of their own fields: FUNDING.yml (sponsor platforms and names), CITATION.cff (title, authors, version and DOI), and CODEOWNERS. In Code Owners, type a path in Who owns this path and press Look Up to hear which rule owns it and its owners. Press Check Owners to ask GitHub whether every owner exists and can write to the repository. GitHub quietly skips an owner who cannot, so a rule meant to protect a folder can protect nothing. Each owner gets one line in What the check found, problems first: no such account, no such team, or access below write. An email address cannot be checked from here and is listed as unchecked rather than passed, and so is any owner GitHub did not answer for.

Choose a search, press Ctrl+E to move to the filter box, type, and press Enter. Plain words narrow the list you are looking at; GitHub’s own words, such as is:open author:@me label:bug, ask GitHub. Ctrl+3 goes to Search, and Ctrl+8 to Saved Searches; Ctrl+N in a search keeps it there.

A search you use all the time can have a place of its own in the tree. In Saved Searches, choose Pin as Node on its context menu: it appears under Saved Searches, named by the search, and opening it asks GitHub for the results afresh. Unpin Node takes the place away and keeps the saved search; Remove Saved Search takes both.

Besides issues and pull requests, code, commits, security advisories and repositories, Search has:

People, Gists and Projects

Ctrl+4 goes to People: your profile, your keys, sponsorships, who you follow, who follows you, your teams, your billing, and Find a Person…. Enter on a person gives them a place in the tree, with their repositories and activity. Follow or Unfollow is on a person’s context menu.

A person’s place also lists what GitHub shows of them publicly, read only: SSH Keys, GPG Keys and SSH Signing Keys (check one before giving them access to a server: “SSH key 4, ending abcdefgh.”), Social Accounts, Gists, Starred, Watching, Projects, Packages, and People They Follow: Activity.

Ctrl+6 goes to Projects; each repository’s own Projects are under it, Ctrl+Shift+7. Chapter 4 covers Projects.

Profiles

People > My Profile is your own profile, and every person’s place in the tree starts with Profile, theirs. GitHub’s profile page is a picture, with a calendar of green squares; here it is rows, each whole on its own:

Set Your Status… (Ctrl+Alt+S) sets your own GitHub status: a message, an emoji, busy or not, and when it clears.

My Keys

People > My Keys lists the keys GitHub keeps for you, all three kinds together, one sentence each:

The SHA256 fingerprint is the same one ssh-keygen -lf prints for the key on your computer, so you can tell which key is which without reading the key itself.

Ctrl+N there adds a key. QUILL asks which kind, then whether to read it from a file, starting in your .ssh folder, or paste it, then a name, suggesting the name written at the end of the key. It checks the key before sending: an SSH key where a GPG key belongs, or anything that is a private key, is refused with a sentence saying so, and nothing is sent. You hear “Added SSH key Laptop” and its fingerprint.

Delete Key… on a key’s row, or the Delete key, asks first and says what stops working without it: pushing over SSH, or commits showing as Verified.

Sponsorships

GitHub Sponsors lets you pay someone for their open-source work, each month or once. People > Sponsorships lists both directions: “You sponsor sam: $5 a month, since 2025-02-01.” and “jo sponsors you: $25 once, since 2026-03-04.”

Every person’s place in the tree has Sponsor. Its first row says whether they take sponsorships, whether you sponsor them already, and what they say about it; each row after it is one of their tiers, with its price: “$5 a month: Coffee. Keeps the lights on.”

Sponsoring spends real money, so QUILL is careful:

My Billing and Usage

People > My Billing and Usage reads this month’s metered use of your account from GitHub’s billing report: one row per product, such as Actions minutes or Codespaces storage, each with its amount and what it costs after discounts, and a last row with the month’s total. It is read only; Enter opens your billing page on GitHub.

GitHub shares these figures only with a token that is allowed to read your plan: a classic token with the user scope, which Sign In with GitHub asks for, or a fine-grained token with Plan read permission. Without that, the list does not pretend you used nothing. Its one row says which permission is missing and that the same figures are on GitHub’s billing page.

Gists

Ctrl+5 goes to My Gists.

Lists of settings

Many of the things GitHub keeps as lists, such as secrets, issue types or the repositories a setting covers, are places in the tree that all work the same way. Each row reads as a sentence. Ctrl+N adds one, where GitHub allows it; Change… on the context menu changes the selected one; Delete deletes it, after asking. Where a list can only be read, it says so when it is empty, and the context menu has no Add or Delete.

Under People, for your own account:

Under an organization:

Under a repository:

Watches

Ctrl+7 goes to Watches: rules, kept on this computer, that tell you when something happens on GitHub. Each row is one rule: a run finishes on a repository or branch, a review arrives on a pull request, a new release, or a new comment.

Watches are checked on the same interval as notifications, set in Workbench Options, while the Workbench is open, and each row says when it was last checked. A watch never marks a notification read, and it changes nothing on GitHub. It is not the same as watching a repository on GitHub, which is Watch or Unwatch on a repository’s context menu and sends notifications.

Why Ctrl+3, Ctrl+4 and Ctrl+8 go places here

Elsewhere in the family, Ctrl+3, Ctrl+4 and Ctrl+8 are AI keys: a document task, Choose Your AI, and Which AI Am I Using. The Workbench has no AI menu, so here they keep their place in the Go row with the other digits: Ctrl+3 is Search, Ctrl+4 is People and Ctrl+8 is Saved Searches. Switch back to the editor (Ctrl+Shift+E) and they are AI keys again.

Across Repositories

Ctrl+0 goes to Across Repositories: one kind of thing from several repositories, in one list. It is for questions such as “what has been released across all my projects this month?” or “which runs failed anywhere?”.

The repositories you read come from a repository set. Repository Sets, under Across Repositories, lists your named sets. Ctrl+N there makes one: choose repositories from a checklist, make the set from a filter such as org:name topic:x, or take every repository you can reach. Enter on a set uses it; Rename Set…, Edit Repositories… and Set Filter… change it, and Delete forgets it after asking. Sets stay on this computer, for the account you are signed in with. Ctrl+N on Across Repositories itself edits the repositories of the set in use.

Under it are eight lists, each drawn from every repository in the set at once:

Every row starts with its repository, “owner/name: #42 Fix the crash”, and the details pane names the repository too, so Enter, Shift+Enter, Comment and the other commands act on the right one. Rows are newest first. Each repository gives at most 100 rows to a list, so one busy repository cannot crowd out the rest. Next Repository and Previous Repository, on a row’s context menu, jump to the next repository’s rows, and View More from This Repository reads more of one.

The status bar says how many rows came from how many repositories, and names every repository that could not be read and why, such as “not found, or no access” or “Discussions are off”. A repository never just goes missing from the list. A fork whose upstream is also in the set adds no issues of its own, because on GitHub a fork’s issues are its upstream’s; the status bar says so, and you read them once, under the upstream.

Fleet has one line per repository in the set: the exact revision of its default branch, its checks, open pull requests, latest release and alerts, and when it was read. A repository that could not be read keeps its line, with the reason.

Each name across the set

GitHub keeps a label, a tag or a secret inside one repository, but you think of them by name across many: “the bug label”, “the v3.2.0 tag”, “the NUGET_KEY secret”. Across Repositories has a place for each such kind, in four groups:

A row is one name, such as “v3.2.0: in 4 of 4 repositories, 4 different commits” or “main: in 30 of 30 repositories, default in 30, protected in 26”. Enter shows its variants, each with the repositories that have it, and the repositories that lack it. A repository that could not be read, often because reading secrets, webhooks and keys needs admin access, is named apart and never counted as missing.

The context menu then changes it everywhere, as far as GitHub allows. Every change shows a preview first, repository by repository, with what is blocked and why, and then one result per repository. Each target is read again just before it is written, so one somebody changed on GitHub meanwhile is left alone and named.

Secrets, environments, webhooks, deploy keys and rules decide who may deploy, what is kept secret or where data is sent, so changing them across repositories needs Full in the Workbench.

Doing things to what is selected

Enter does the obvious thing; the Applications key, or Shift+F10, opens the context menu, with the obvious thing first and Properties last; and Alt+Enter shows everything about the selected row on one sheet (Chapter 13). The Item menu (Alt+I) has the same commands as the context menu.

The keys you will use most:

Key Does
Ctrl+Shift+M Comment on the selected issue or pull request
Ctrl+Shift+I Read the selected issue, pull request or discussion as one document
Ctrl+Shift+D The selected pull request’s changed files
Ctrl+Shift+Enter Merge the selected pull request
Ctrl+Shift+W Say what failed in the selected run
Ctrl+Shift+F5 Run the failed jobs again
Ctrl+Shift+B Compare the selected branch with another
Ctrl+Shift+A Assign the selected issue to Copilot
Ctrl+Shift+T Start the selected issue or pull request in a local worktree
Ctrl+D Keep the selected row under Favorites, or take it out
Ctrl+Shift+C Copy the selected row’s address
Shift+Enter Open it on GitHub, in your browser
Delete Remove it safely: mark a notification done, close an issue after asking

Delete always does the safe thing for the kind of row, and asks first whenever it cannot be undone: on a branch, a label, a release’s file, a gist, an Actions cache or a workflow run it deletes that one thing, after asking. It never deletes the repository’s default branch. Enter never deletes anything.

Taking a list with you

Export List… (Ctrl+Shift+X), on the Workbench’s File menu, saves the list you are looking at, as it is shown: its columns, its filter and its rows. Choose an Excel workbook, a CSV file or a Markdown table in the Save window. A Markdown table is the kind the editor reads as a table, so the Workbench offers to open it there, where the table keys move cell by cell. It then says how many rows it wrote, and names any columns you have hidden, because those are left out. It works on any list: issues, pull requests, runs, alerts, people, Change History. The WordPress Workbench’s Export List is the same command.

An alert list exports without anything secret in it. The Workbench never asks GitHub for a secret scanning alert’s value, so it is in neither the list nor the file. Text GitHub wrote into an alert, such as a code scanning message quoting a hard-coded password, passes the same redaction Change History uses before it is written: a value shaped like a token or key becomes [TOKEN], and a link’s user name and password are dropped. When that happens, the Workbench says how many values it held back.

Bringing issues in

Two rows on the Workbench’s File menu make many issues at once in the repository you are in. Neither sends anything before you have read a preview and pressed Create Issues; Cancel there sends nothing.

Afterwards a window lists each row or line with the issue it made, or why GitHub refused it, and Change History has each issue made.

Each kind of row’s own commands

Everything happens in the Workbench, on the selected row; where a job needs a window, such as a run’s logs, that window opens in front of the Workbench and blocks only the Workbench, never the editor. Each row’s context menu has its own list, the commands you use most first and the rest under More, and Shift+F1 reads it with the keys:

Summarize Discussion uses the AI connection of the editor that opened the Workbench, and Start in Local Worktree uses its local Git. When the editor has not given the Workbench either one, the row is greyed and says why.

What you hear afterwards

Every change asks first when it cannot be undone, runs without freezing the window, and says one sentence about what GitHub confirmed. F9 says it again.

Those sentences follow the same setting as the editor’s copy and paste, When a command does something, give me (QUILL Guide, chapter 11):

F9 says the last result even when you only heard its sound. Chapter 10 lists the refusals and what to do about each.

More commands on rows

Many rows also have commands that make one call to GitHub and say what came back, or show a longer answer in a window to read and copy. They are on the row’s context menu (Shift+F10, under More when the menu is long) and on the Item menu. Each asks before it changes anything, and anything that holds a token (a runner’s setup or removal commands) goes to the clipboard and is never said or shown. Here they are by what you are doing.

Learning about a repository

Looking after a repository

Builds and runners

Reviews, issues and discussions

Security

Organizations and teams

Projects

Your own account

Copilot

A few of these use parts of GitHub newer than the description QUILL was built against (closing references, a Project’s views and issue fields). Those first read from GitHub what the change needs, and if GitHub has changed it, they send nothing and say to use Open on GitHub instead.

Hearing where you are

Alt+1 to Alt+9 say something and move nothing: where you are, what is selected, the selected item’s state, the counts, your access, GitHub’s hourly allowance, the filter, what is loading, and your account. F9 says the last result again, and Shift+F9 explains it: what it means, and what you might do next.

Emoji by name

People write emoji on GitHub as shortcodes, :tada: or :+1:, which the website shows as pictures and a screen reader would otherwise spell out, colons and all. In the details pane, and in Read as Document…, QUILL reads each one by its name instead: “Shipped 🎉” is “Shipped party popper”, and :+1: is “thumbs up”. A shortcode inside code, between backticks or in a code block, is left as typed, since there it is code, and so is one QUILL does not know.

Help and Learning

The last place in the tree is help you can walk through like any other list.

Once in a while a tip also comes to you at the right moment: the third time you do something the long way (arrow through a long list without the filter, open Properties on one row after another, press Load More again and again), the tip for the short way is added to the end of the details pane, once, and is not spoken, so it interrupts nothing. Offer a tip when it would help, in Workbench Options, General, turns those off; they all stay in Tips. Words are explained by QUILLBee, QUILLBert’s friend, in one line each. Plain help, without QUILLBert and QUILLBee, in Workbench Options, General, says the same words without the two names.

F1 ends with an example from your own work when the window knows enough: the repository you are on and the row you have selected (“On Community-Access/quill, #42 Crash on start is selected: Alt+Enter opens everything about it”), or the account you are signed in as. It uses only what the window has already loaded, and sends nothing anywhere.

Help > Take the Tour (Alt+Shift+T) is a spoken tour of the window, a pane at a time: what the pane is, and one thing to do there. F6 moves on to the next pane and the next step, F1 says the step again, Shift+F1 lists the steps, and Escape skips the rest. The tour starts by itself the first time you open the Workbench, once, unless Show First time here? help is off.

Help > Ask How… (Alt+Shift+A) takes a question in your own words, such as “how do I keep only the issues with a word in them?”. The answer is built only from this help (the tasks, places, words and options, and every menu row with its key), by the AI you chose in the editor’s Choose Your AI. When the help does not cover the question it says so, and when nothing in the help comes near the question the AI is not asked at all. The answer is shown in a list, with a Do It row for each command it names; nothing runs until you choose a row. Only your question and the help’s own words are sent: no repository, token or GitHub content. It is greyed without an AI connection, and off in Safe Mode.

The keys are also on a key card you can print or emboss, made from the same key table as the window: docs/github/key-card.html to print, and docs/github/key-card-braille-ready.txt, laid out 40 cells by 25 lines a page, for QUILL’s Braille Mode or a braille translator to make the BRF. The whole of this guide is also one book, github-guide-book.epub, beside these pages.

The help keys work everywhere in the window:

Key Answers
F1 What this place and this control are for
Shift+F1 What can I do here, with each key
Alt+F1 What the GitHub word for the selected row means
Ctrl+F1 This guide, at the chapter for where you are
Ctrl+Shift+F1 Search all of help: places, commands, words and tasks
Alt+Shift+F1 Every key in the window
Ctrl+F2 Help > Tutorials: the GitHub lessons, under Help and Learning
F11 Say or Type a Command, in this window
Ctrl+Alt+Shift+F1 What Can I Say Here: what F11 can do in this window
Ctrl+Alt+K Key Describer: press keys to hear what each does here, without doing it; Escape stops

Why? explains something the Workbench did on its own, with no key from you. When there is something to explain, Shift+F1 lists Why? first, and watch and notification rows also have it on their context menu. It covers:

Shift+F1 already says why a command is greyed, and a sheet says why a field is read-only beside the field.

Say or Type a Command

F11 works here as it does in the editor, with this window’s own commands. Type what you want, such as “show the pull requests”, “what failed” or “how much rate limit is left”, and press Enter. Only the Workbench’s commands are offered, and each runs exactly as its menu row would: a change still asks and previews first, and a Read Only account is still refused. Commands that send a change by themselves, such as Merge or Close, are not offered from a sentence; their menu rows and keys still work.

Help > What Can I Say Here? (Ctrl+Alt+Shift+F1) lists what you can ask for in this window, with an example for each. In this window, requests are matched on this computer only and are never sent anywhere.

For a change to many items at once, described in words, use Tools > Plain-Language Batch… (Ctrl+Shift+S) instead. Chapter 13 covers it.

Dry Run

Tools > Dry Run (Ctrl+Alt+D) is a switch for the whole Workbench. While it is on, every command still asks its questions and shows its preview exactly as usual, and then, at the moment it would change something on GitHub, it stops and says what it would have sent: “Dry run: QUILL would send PATCH /repos/octo/app/issues/7 (state, state_reason). Nothing was changed.” Lists, sheets, previews and everything else that only reads keep working.

It is for learning a command without consequences, and for checking a big batch twice before you send it for real. The Account cell of the status bar says “Dry Run: nothing is sent” while it is on, and it stays on until you press Ctrl+Alt+D again or close QUILL. Local Git work, such as making a worktree, does not touch GitHub and is not stopped.

The GitHub API Console

Tools > GitHub API Console… (Ctrl+Shift+J) sends any GitHub REST request or GraphQL query you type, for the times no command does what you need. It completes paths from GitHub’s own description of its API, says what a request does and what it needs before you send it, and shows the answer as a tree you can arrow through. A GET only reads. Any other method changes something, so it needs Full in the Workbench and asks you to type the method before it sends. Dry Run stops it like any other change.

Practice on GitHub

Help > Practice on GitHub… (Ctrl+Alt+P) makes a private repository in your own account, quill-practice, to learn the writes on, where nothing matters. After asking, QUILL fills it with:

You hear each part as it is made, and then the Workbench opens the repository. The next time, the same command offers Open It, Delete It and Start Over… and Delete It…; both deletions ask first. GitHub lets an app delete a repository only when you signed in with the delete_repo permission; without it, QUILL says so and tells you where on GitHub to delete it yourself.

Is it GitHub, or is it me?

When GitHub is slow or failing, the Workbench’s errors can look like your own mistake. Help > GitHub Service Status… (Ctrl+Alt+F1) reads GitHub’s public status page, www.githubstatus.com, and says whether GitHub says everything is working, which parts are slow or down, and any incident GitHub is working on, with its latest update. It asks the first time, reads the page only when you choose the command, and is greyed in Safe Mode. Chapter 10 has more.

Workbench Options

GitHub’s preferences live in the Workbench, not in the editor’s Options: Tools > Workbench Options…, Ctrl+Shift+O. It has five pages:

Lists also has Short rows for braille: each list row becomes one short line for a braille display, the number and title first, no column names, and short words (cl for closed, PR for pull request, 3c for three comments, 9 Nov for a date). Nothing is cut off, and Details still says everything. Columns… still chooses what the line holds. General has Offer a tip when it would help and Plain help, without QUILLBert and QUILLBee.

Each account’s Workbench level, Read Only, Organize or Full, is not here: it is Account > Roles and Access > Workbench Level for This Account… (Chapter 13).

You never have to open Workbench Options: the Workbench works as it comes.

A walk-through: finding your way on the practice repository

This takes about five minutes and changes nothing on GitHub. If you have not made the practice repository yet, press Ctrl+Alt+P first and say yes.

  1. Open the Workbench from GitHub > Open GitHub Workbench. You hear “GitHub Workbench” and the place it opened on.
  2. Press Ctrl+9. You are on Start Here; F6 and then the arrow keys read its details. Press Shift+F6 to come back to the tree.
  3. Press Ctrl+L, type quill-practice, with your login in front, such as jeff/quill-practice, and press Enter. The repository gets a place of its own and you are on it.
  4. Press Ctrl+Shift+1. You are on its Issues, and the list loads three issues. Press F6 to reach the list.
  5. Arrow to the typo issue and press Shift+F1. You hear what you can do with an issue, with each key.
  6. Press Alt+Enter. Its Properties sheet opens; Escape closes it without changing anything.
  7. Press Ctrl+Shift+4. You are on Actions, Runs, with the practice run that failed on purpose. Press Ctrl+Shift+W to hear what failed.
  8. Press Alt+1. You hear where you are. Press Backspace to go back to the issues, with the typo issue selected again.
  9. Press Ctrl+F1. This guide opens at the chapter for where you are.

Learn it with a guided lesson

Help > Tutorials (Ctrl+F2) has the GitHub lessons. For this chapter: