Chapter 13: Properties, filters and permissions
What this chapter covers
On GitHub’s website, the facts about an issue or a repository are spread over a page, with the controls to change them tucked into menus and side panels. In the Workbench, everything about one thing is on one sheet, and the sheet is where you change it. This chapter is about that sheet, and about the two questions that come with changing things: which ones, and am I allowed?
You open a Properties sheet and change a field, change many things at once, say a change in words, undo a change, and filter and shape a list. Then you look at permissions: what you are allowed to do, how to get what you are missing, what the Workbench itself allows each account, and who else has access and why.
By the end you will be able to change anything the Workbench shows, safely, and answer “why can’t I?” and “who can?” without leaving the window.
Properties: Alt+Enter on anything
Select a row in the list and press Alt+Enter. A
Properties sheet opens for it: an issue, a pull request, a repository, a
label, a milestone, a branch, a release, a workflow run, a person, a
team, a gist, an alert, and the rest. Item >
Properties… and the last row of every context menu open the
same sheet. In the tree, Alt+Enter on a repository opens
the repository’s own sheet.
The sheet is a set of pages. The first is always General.
Ctrl+TabandCtrl+Shift+Tabmove between pages, andCtrl+1toCtrl+9jump to one.- Every fact is a box you can Tab to and read, even the ones you cannot change, so a braille display can pan through them. Dates are written out.
F5loads it again from GitHub.Ctrl+Shift+Ccopies the whole sheet as text, and the Copy Link and Open on GitHub buttons do what they say.
The sheet remembers the page you used last for each kind of thing. If you set milestones all morning, the next issue’s sheet opens on Organize.
Changing things
A field you are allowed to change is an ordinary control. A field you
are not allowed to change is read-only, and the line under it says why,
for example “changing this needs triage access to owner/name; you have
read access”, and who can change that. F1 on the field says
the same.
- Labels, assignees, reviewers, Projects and your reactions are lists of check boxes, and a repository’s features (Issues, Projects, Wiki, Discussions) are check boxes too. Each one says its state in its own words, “bug, on” or “Issues, off”, and Space checks or clears it once; the words change with it, and nothing else is said. Unchecking a Project takes the item out of it, along with whatever the project’s own fields said about it, so that one cannot be undone.
- New Label…, New Milestone… and New Project… beside their lists make a new one on GitHub and check it straight away. If one by that name is already there, that is not a failure: QUILL says “bug already exists; using it” and checks the one GitHub has.
- An issue’s Issue type and a pull request’s Into branch are lists too, of the types your organization has and the repository’s branches. New Issue Type… makes a type for the whole organization, which needs an organization owner. New Branch… makes a branch from the one the pull request merges into now, then selects it. “(none)” clears an issue type, but a pull request always merges into some branch, so choosing “(none)” there leaves it as it was and QUILL says so.
- An issue’s Issue Fields page edits its organization’s issue fields, each with its own kind of control: a date, a number, a single choice or text. Saving sets only the fields you changed and reads the issue again to check GitHub kept them; emptying a field clears it. A field with several choices, or of a kind QUILL does not know, stays read only. Without triage access the page says why each field is locked.
- OK saves and closes, and Enter on a check box, a
list or a one-line box is OK. Apply, or
Ctrl+S, saves and keeps the sheet open, and focus comes back to the check box or field you were on.Ctrl+Enteris OK from anywhere, even in a long text box. Escape is Cancel.
The context menu of an issue or pull request still names the common
changes: Edit Title…, Labels…,
Assignees…, Milestone… and
Projects… open the sheet with focus already on that
field. There are no separate keys for single properties:
Alt+Enter, then the page.
You: your own relationships
Anything you can have a relationship with has a You
page, right after General: the second page, so Ctrl+2
reaches it. It holds every relationship GitHub offers with that thing,
each as a control you change like any other field, and saving sends only
the ones you changed and says what happened in one sentence:
“owner/name: starred on; watch level all activity.”
- A repository: Starred, and Watch level (all activity, participating and mentions, or ignore).
- A person: Following and Blocked.
- An organization: Following, and Show my membership publicly.
- An issue: Subscribed, your reactions (a check box for each of the eight), and Pinned to the repository.
- A pull request: Subscribed and your reactions.
- A discussion: Subscribed, your reactions and Upvoted.
- A release: your reactions. A gist: Starred. A notification: Subscribed.
Some relationships GitHub’s API cannot change, and those are
read-only boxes whose F1 says why in one sentence: whether
something is Pinned to your profile (customize your
pins on your GitHub profile page), whether you are
Sponsoring someone (that spends money at a tier you
choose, so it is done from their Sponsor node, never a check box),
whether a pull request or a discussion is pinned (GitHub pins only
issues through its API), and whether somebody follows you, which is
theirs to change. The menu rows you already know, such as Star or
Unstar, Watch or Unwatch, Follow or Unfollow, React… and Pin or Unpin
Issue, send the same requests as the You page. Read Only and Safe Mode
lock the You page like every other page, with the reason under each
field.
The rest of the relationships, and every one as a row on the context menu too, each saying its outcome in one sentence:
- A repository’s You page also has Star lists (your lists, the ones holding it checked, as Star Lists… sets them), Forked by you (check it to fork the repository to your account; a fork is a repository of its own, so clearing the box is refused and says where to delete it), and the read-only Sponsoring the owner. The rows Fork… and Sponsor the Owner… are on the repository’s context menu: Sponsor the Owner opens the owner’s Sponsor tiers, and nothing is charged until you choose a tier with Sponsor at This Tier… and type their name.
- In Favorites and Pinned in the Workbench close a repository’s You page, and In Favorites an issue’s and a pull request’s. These live on this computer, not on GitHub, so they change at once, as the Favorites and Pin rows do.
- Subscribe or Unsubscribe… on an issue, a pull request, a discussion or a commit: all activity, or only when you take part or are mentioned.
- Block or Unblock… on a person.
- Block from Organization… on an organization (it asks whose account) and on a member in its Members list; its Blocked People list unblocks. Leave Organization… asks first. Your Invitation says whether the organization has invited you: Accept Membership joins, and since GitHub’s API cannot decline an organization’s invitation, it gives the page where GitHub does. A repository’s invitations have Accept and Decline rows.
- React to a Comment… on an issue or a pull request (its conversation and its line comments) and on a discussion (comments and replies): choose a comment, then a reaction; one you gave already is taken back. On a commit, React to a Commit Comment… reacts to its comments, and Commit Comments… reads and adds them. GitHub’s API reacts to a commit’s comments, never to a commit itself.
Saving safely
- If somebody else changed it meanwhile, the sheet says so before anything is sent: “Changed on GitHub since you opened this: milestone is now 2027.2.” For each such field you choose Keep Theirs or Use Mine. Lists you add to and take from (labels, reviewers, Projects) never ask: only your own additions and removals are sent, so a label somebody else added while you had the sheet open stays on.
- Only what really changed is reported. After saving, the Workbench reads the object again and says one sentence about what changed: “Issue #42: added bug, removed docs.” GitHub sometimes accepts a change it then ignores, usually because of access; when that happens the sentence names the field.
- A field GitHub needs is never sent empty. Emptying a title, a name, a tag or a retention period leaves it as it is, and QUILL says so: “Title cannot be empty on GitHub, so it was left as it is.” A number box must hold a whole number; anything else is said before anything is sent.
- Rulesets, branch protection and environments are sent whole, so each save rebuilds them from what GitHub has at that moment. A rule somebody else changed while your sheet was open is kept, including one you chose Keep Theirs for.
- Access and settings are previewed. A change to who has access, or to a repository setting, is read back to you in words first, and Enter goes ahead. Anything hard to reverse, such as making a private repository public, also asks you to type its name.
Many at once
Select several rows (Shift and Ctrl with the arrows, or
Ctrl+A) and press Alt+Enter. One sheet opens
for all of them, titled “Properties of 5 issues”.
- A field that is the same on all of them shows its value. One that differs says Mixed and is left alone unless you change it.
- A label on some of them is a check box in its third state, read as “bug, on 3 of 5”. Check it to put it on all of them, clear it to take it off all of them, or leave it.
- You hear a preview first: “Change 14 issues: add bug, remove triage. 3 of them already have bug.” Enter goes ahead.
- Then a list of results, one line per item: Done, Skipped because it
was already so, or Failed and why. Copy Results copies them, and Retry
Failed (
F8) runs the failed ones again. Each is read from GitHub afresh first, so a field that took the first time counts as already done. - The You page works here too. Select twelve repositories in a search,
press
Alt+Enter, and check Starred or set Watch level on the You page: each repository is starred, or watched, with a result line for each.
Batches pause a second between items, because GitHub limits how quickly one account may make changes.
Saying it in words
Tools > Plain-Language Batch…
(Ctrl+Shift+S) takes the change as a sentence, for the
repository you are in:
- “close every issue labelled duplicate older than 90 days”
- “close all issues labeled stale that nobody touched in 90 days as not planned”
- “add label triage to every issue with no label”, or “remove label wontfix from all closed issues”
- “assign alice to every open issue labelled bug”, or “unassign me from all pull requests”
- “which pull requests are waiting on me, oldest first?” shows them in the list, and “how many issues are labelled bug?” says how many. Neither changes anything.
There is no AI in it. QUILL reads a fixed set of words: labelled, without label, with no label, by, assigned to, unassigned, in milestone, waiting on me, mentioning me, open or closed, an age (“older than 90 days”, “updated before March 2024”), and oldest or newest first. The same sentence always means the same thing, and a word it does not know is never guessed: it says what it does read, and gives you your sentence back to correct.
It then searches GitHub and shows every item it found as a checked
list. Uncheck any you want left alone, and OK goes on to the same
preview and results as any batch above: “Change 12 issues: state to
closed as completed.” Closing as a duplicate is not a batch, because
each one needs the issue it duplicates; close those one at a time with
Delete on the row. The WordPress Workbench’s Plain-Language
Batch reads ages the same way.
Undoing a change
Ctrl+Z in the list or the tree undoes your last change
on GitHub, where GitHub allows it, and Ctrl+Y makes it
again. In a text box they undo and redo your typing as usual. The same
commands are Edit > Undo GitHub Change and
Redo GitHub Change.
Undo reads the object from GitHub first, so a milestone goes back as the milestone it was and a ruleset keeps its other rules. If somebody changed the field since, Undo stops and says so rather than overwrite them. A redone change can be undone again. A change GitHub cannot reverse says why in its preview, before you save it, and again if you ask to undo it: a secret’s old value is never given back, and taking an item out of a Project deletes its field values there.
Account > Change History…
(Ctrl+Shift+H) lists every change the Workbench has made,
newest first: what, when, before and after, and whether GitHub confirmed
it. Undo This Change reverses the selected one. You can save the list as
a CSV file or clear it. It stays on this computer for 90 days, and a
secret’s value is never in it.
Account > Set Your Status…
(Ctrl+Alt+S) reads your GitHub status, the short message
beside your name, and offers to set a new one or clear it. A new one
asks, a question at a time, for the message (“Back Monday”), an emoji by
its GitHub name (palm_tree, house, or none),
whether to mark yourself busy, which tells people asking for your review
that you may answer slowly, and when it clears itself: never, in 30
minutes, an hour, four hours, tomorrow or in a week. You hear the status
as it is now.
Filtering
The filter box (Ctrl+E) takes plain words, which narrow
the loaded list, and GitHub’s own search terms such as
label:bug or no:milestone, which ask GitHub.
Three other ways write into the same box.
- View > Quick Filters: Assigned to Me, Assigned To…, Opened by Me, Opened By…, Mentions Me, Review Requested from Me, Reviewed by Me, No Assignee, No Milestone, No Label, No Project, No Type, Drafts, Has Conflicts, Checks Failing and Updated This Week. Each one is checked while it is on, they combine, and the window title names them. Clear These Filters turns them all off.
- Show Only and Hide: the context menu of a row has both, with every value in that row: “label bug”, “author dependabot”.
- The Filter Builder,
Ctrl+Alt+F: choose an attribute, an operator and a value, then Add Condition (Insert). Each box reads its own label as you Tab to it: Attribute, Operator, Value. The values come from the repository, and Me is offered for every person. The query appears as you go, so you learn GitHub’s syntax by watching it. OK puts it in the filter box; Save as Search also keeps it under Saved Searches.
Has Conflicts is the one GitHub’s search cannot answer, so the
Workbench checks the pull requests already loaded and the Items cell of
the status bar says so. View > Load All
(Ctrl+Shift+Page Down) loads every page to be sure.
Filtering every other list
Branches, tags, commits, releases, workflows, runs and the other lists are read whole, so the words before a colon are checked here, over the rows already loaded. Each list answers its own:
- Branches:
name:,protected:,ahead:,behind:,author:(the last commit’s) andcommitted:(its date). - Tags:
name:andsha:. Commits:author:,committed:,message:(words in it) andsha:. - Releases:
tag:,name:,draft:,prerelease:andcreated:. Release assets:name:,size:,downloads:,type:andupdated:. - Workflows:
name:,path:andstate:. Runs:workflow:,branch:,event:,status:,conclusion:,created:andsha:. - Every other list (repositories, labels, milestones,
notifications, packages and the rest):
name:,repo:,owner:andupdated:.
A name takes * as a pattern
(name:release-*). A minus in front leaves those out
(-conclusion:success). Numbers and dates take
>, <, >=,
<= and a range with two dots (ahead:>=3,
created:2026-01..2026-06); a date can be just a year or a
month. no:repo keeps the rows with none. The Items cell of
the status bar says how many the filter kept of how many loaded, such as
“Filtered here: 2 of 3 loaded. Load All to be sure.”, and names any word
this list cannot filter on, so nothing is quietly ignored.
The Search place’s lists send the whole box to GitHub instead, so
there GitHub’s own search terms work: language: and
stars: for repositories, committer: for
commits, location: for people.
More rows
Every list starts with one page: 30 issues or pull requests, 50 rows
of anything else. Load More
(Alt+Page Down) reads one page more each time, and
Load All (Ctrl+Shift+Page Down) reads up
to a thousand at once. Both work on every list in the Workbench,
Notifications, My Work, discussions, labels and the merge queue
included. When a list holds only part of what GitHub has, the Items cell
of the status bar says so, for example “Gists: showing the first 50
items; more may exist. Load More or Load All reads the rest.”, so a
short list is never mistaken for the whole of it.
Shaping the list
- View > Show chooses issues, pull requests or both, and View > Open or Closed which ones.
- View > Sort By orders the list, and View
> Columns… (
Ctrl+Shift+U) chooses its columns. - View > Group By puts the groups in the tree as nodes: by label, milestone, assignee, author, type, state, repository or review state. Each node reads with its count, and selecting it shows that group.
- Those orders and groups are an issue’s. Every other list (branches, tags, releases, workflows, runs, discussions, notifications, alerts, people, teams, repositories and the rest) has Sort By > By Column… and Group By > By Column… instead: any of its columns, first to last or last to first, and for a list of one column its name, repository, kind or last update. Each list remembers its own choice, for this account, as it remembers its columns.
- Your place is kept. Coming back to a list, with
Back (
Backspace) or from a sheet, a dialog or a document, puts you on the row you left, even if it has moved; a refresh while you are in a group keeps you in that group, on that row. - Go > Next Unread (
Ctrl+Period) and Previous Unread (Ctrl+Shift+Period) move between unread notifications. Go also has submenus for your pinned repositories, favorites and saved searches.
Permissions
Yours
Account > GitHub Permissions…
(Ctrl+Shift+P) lists every permission the Workbench can
use, what it unlocks, and whether you have it, such as “project: set an
item’s projects and edit project fields. You do not have it.”
- Add Permissions… asks for every missing one the next time you sign in with GitHub, so you approve once on GitHub’s page.
- Copy Command copies the
gh auth refreshcommand that adds them for the GitHub command-line tool. - Classic Token Page opens GitHub’s new-token page with the scopes listed, and Fine-grained Steps copies what to set on a fine-grained token, by GitHub’s own names.
- Check Again reads your permissions again and says what changed.
A fine-grained token does not tell anyone its permissions, so for one of those the list says “This token’s permissions are set on GitHub” rather than guessing.
Read Only, Organize or Full
Account > Roles and Access > Workbench Level for This Account… sets what the Workbench may change with an account, whatever GitHub would allow. Read Only changes nothing, which suits demonstrating or looking around someone else’s organization. Organize allows organizing and comments, such as labels, assignees, reactions and closing issues, but not access, settings or deleting. Full allows everything your access allows. Safe Mode makes every account Read Only.
Every change is checked against the level once, before anything is
sent, whether it comes from a menu row, a sheet, a batch,
F11 or the API Console. A change the level does not allow
is refused in one sentence naming the level it needs: “Cannot delete the
label: it needs Full in the Workbench, and this account is Organize;
Account, Roles and Access, Workbench Level for This Account changes it.”
On a sheet, the reason is beside each locked field. Alt+5
says what you can do where you are.
The smallest permissions that would do
Account > Roles and Access > Least Privilege Advice… is a report: it changes no token and no setting. It is based on what the Workbench saw this account do on this computer: the kinds of request it sent (never which repository or person), the changes that passed the Workbench level check and how far each reached, Change History, the scopes GitHub names for a classic token, and every time GitHub refused a request and said which permission it wanted. From those it suggests:
- the smallest Workbench level that covers what you did (Read Only, Organize or Full);
- for a classic token, the scopes that are enough, the ones it has that were never used, and a broad scope where a narrower one would do, with a link to GitHub’s new-token page with just those checked;
- for a fine-grained token, the permissions by GitHub’s own names, read-only or read and write, and what no fine-grained token can reach.
It then says what it cannot know. It saw only this computer’s use,
not another computer, the gh command or GitHub’s website.
GitHub does not list a fine-grained token’s exact permissions, so the
report can say only what worked and what was refused. And it cannot tell
whether a repository is private, so repo is suggested only
where that would matter. To change a token, use GitHub’s Settings,
Developer settings.
Who else has access
A repository’s sheet has an Access page: the people with access, the
teams, and pending invitations. Select a row and use Add…, Change… or
Remove (Insert, F2 and Delete
work too). Each change is read back to you first, and recorded in Change
History. The Workbench refuses to remove your own admin access or the
last owner, and says who else could do it. Organization and team sheets
work the same way for members and maintainers.
On an organization’s sheet, each member reads with their role and whether two-factor sign-in is on: “kim, person, member, direct, two-factor off”. GitHub shows two-factor only to owners; anyone else hears “two-factor not shown to you”. Change… on a member offers member, owner, or outside collaborator; making someone an outside collaborator takes them out of the organization and its teams and leaves only the repositories they were given directly, so QUILL asks you to type their name first. On the Outside Collaborators page, Add makes a member an outside collaborator, Change… invites one to be a member, and Remove takes away every repository they have here, again after their name is typed. You cannot make yourself an outside collaborator, remove yourself while you are the last owner, or remove the last owner.
A team’s sheet lists its maintainers and members, and its Repositories page lists every repository the team reaches with its role there. Add gives the team a repository, Change… changes its role, and Remove takes it away. The last maintainer cannot remove themselves. When you take admin away from a team you are on, QUILL asks GitHub first whether that team is how you administer the repository, and if it is, says so and changes nothing. The General page’s Parent team moves the team under another (empty makes it a top-level team), and New Team… on an organization asks for the parent and whether mentions notify the team.
The organization’s Members list in the tree reads the same way (“kim, member, two-factor off.”), and Delete there asks for the name typed and keeps the last owner. Members Without Two-Factor on the organization’s row lists only those, for owners.
On the pending invitations, Remove cancels the invitation (they can be invited again), and Change… changes the role a repository invitation offers before it is answered. GitHub cannot change an organization invitation’s role, so for one of those, Remove it and invite them again.
Account > Roles and Access also has:
- My Access Here…, your role on this repository and where each part comes from;
- View As Role… and Compare Roles…, what a role may do, read-only;
- Why Can’t They?…, what stops a person doing something, and who can change it;
- Access Review…, every person, team and repository in an organization with their role and where it comes from, copied as CSV too;
- Bulk Access Changes…, one team or person on many repositories at once, previewed person by person, with a result per change;
- Access Templates…, named sets of access, such as
Contributor: write on these repositories and member of a team. Choose
New Template…, give it a name, and write one line for each place:
write on owner/name(read, triage, write, maintain or admin),member of org/teamormaintainer of org/team, andmember of orgorowner of org. A line it cannot read is said and left out. Templates are kept on this computer, for this account, and making one sends nothing; - Apply Access Template…, everything a template holds, given to one person by login in one batch: organization first, then teams, then repositories. The preview says every change in words and asks once; each change then has its own result and its own line in Change History. It needs Full for this account in the Workbench, as any access change does;
- Compare Accounts…, two of your signed-in accounts on this repository, side by side;
- Act As Another Account…, one action done as another of your signed-in accounts.
Every one of these answers from what GitHub itself says, and each
line names the reply it came from, such as “(GitHub: /repos/acme/web
permissions)”. My Access Here reads the repository’s permissions,
GitHub’s own viewerPermission, your role name (a custom
role is named too), your place in the organization and its base
permission, the teams that give you access, the rules on the default
branch, and this sign-in’s scopes. Why Can’t They? reads the person’s
real role from GitHub rather than asking you for it, then the rules
GitHub says apply to the branch, and names the one that stops them.
Two things GitHub does not say, and the Workbench says so rather than guessing. GitHub’s API does not list what a role may do, so View As Role and Compare Roles show GitHub’s documented defaults for its built-in roles, say that is what they are, and then list who on this repository GitHub says has each role; a custom role is named, but what it adds is on the organization’s Repository roles page. And GitHub does not list a fine-grained token’s permissions: My Access Here says so, and when GitHub refuses something, the Workbench says the permission GitHub named in its refusal. When GitHub will not tell your account something at all (only people with write access may read others’ roles, for example), the answer says it cannot be known.
Bulk Access Changes reads each repository’s current role first, and the preview says it per person: “kelly on acme/web: write now, maintain after.” A repository where they already have that role is listed as “nothing is sent”, and nothing is.
Compare Accounts and Act As
With more than one account in Manage GitHub Accounts, Compare
Accounts… asks GitHub, with each account’s own sign-in, about
the open repository: its role, viewerPermission, its role
name and its sign-in’s scopes, then what one may do that the other may
not. Before showing anything under an account’s name, it asks GitHub
whose the saved token is; if GitHub names somebody else, nothing is
shown for that account, and you are told to sign in again.
Act As Another Account… does one thing as another of your accounts and then forgets it: approve the selected pull request (approving your own needs a second account), comment on the selected issue or pull request, close or reopen it, or star the repository. You choose the account, then the action. The question names the account and its server (“As kelly-test on github.com, not as you: approve pull request #7”), and so does the result (“Approved pull request #7 in acme/web as kelly-test.”). Act As is held to that account’s own Workbench level, not yours, and Safe Mode stops it like any write. It checks whose the token is first, and sends nothing if it is not that account’s. Your own account, its lists and its remembered reads are never touched: everything QUILL remembers is kept per account.
Who has what, and why
Under an organization in the tree, three lists answer “who can do what here” a row at a time, so you never have to read a grid:
- Access Review: People has a row for every person and repository pair, with the role they really have and where it comes from: “jeff on quill: Admin, from team Maintainers; also Write directly; also Read from the organization’s base permission.” The highest comes first; every other way they have access follows “also”. An outside collaborator’s direct access says so, and an owner’s reads “from being an owner of the organization”.
- Access Review: Teams has a row for every team and repository pair: “Docs on site: Reviewer, for 3 members, a child team of Maintainers.”
- Custom Property Values has a row a repository with every custom property, unset ones said as “not set”: “site: tier is not set; areas is docs and ui.”
Type a name, a role or a team in the filter box, or use Show Only, to
narrow any of them, and Export List…
(Ctrl+Shift+X), on the Workbench’s File menu, saves what is
shown. When GitHub will not show part of the answer, for example a
repository’s direct collaborators to someone who is not its admin, the
status bar says which, rather than leaving people out silently.
Set Repositories’ Custom Property… on the
organization’s row gives one property a value in several repositories at
once, and Issue Types under the organization lists its
issue types.
Rules in plain words
A ruleset’s sheet, and a branch’s protection, list every rule as a check box with its settings, and a Summary page reads the whole thing as sentences: “On the default branch: changes need a pull request with 2 approvals including a code owner; checks build and test must pass; force pushes are blocked.” Read that page first.
A repository’s Settings > Rulesets list, and an organization’s Rulesets, show each ruleset as a sentence; Alt+Enter opens its sheet, and Delete removes it after you type its name.
- The Rules page also has Every rule and its settings, a line a rule with every setting GitHub sent: file paths, file sizes, patterns, workflows, code scanning tools, and any rule type QUILL has no check box for yet.
- The Bypass page has a check list of the roles that may bypass the rules (organization admins, admins, maintainers, writers, deploy keys), and lists everyone who may, teams and apps included. Teams and apps you have not changed are kept as they are.
- An organization ruleset’s Repositories page says which repositories it covers, by name or by a custom property, and lets you choose them by name, and stop those repositories being renamed out of it.
- A branch’s classic protection sheet has every setting GitHub offers: approvals, stale approvals, code owners, the most recent push, status checks and up to date, signed commits, administrators, linear history, force pushes, deletion, conversations, blocking new branches, locking the branch, and fork syncing. Its Who page says who may push, dismiss reviews and skip the pull request; saving keeps those lists exactly as they were.
- Rule Insights under a repository’s settings, and under an organization, lists the pushes its rules passed, blocked or let through.
An organization’s roles
GitHub gives every organization roles that reach all its repositories at once: All-repository read, triage, write, maintain and admin, the security manager, the app manager, and any custom roles. Choose Roles… on an organization’s row (in the Workbench’s Organizations place) to open Roles in that organization.
- Roles lists them, each with what it is based on and what it is for. Choose one, and Who holds it fills with its people and teams, each row starting with “Person:” or “Team:”. A person who holds the role because of a team says so: “Person: kim, through docs”.
- Give to Person… (
Alt+P) asks for a GitHub username; Give to Team… (Alt+T) asks for the team’s short name, as it appears in the team’s address. - Take Away… (
Alt+A) asks whether the selected person or team should lose only this role or every organization role. A role that comes through a team is taken from that team instead, and QUILL says which.
After each change QUILL reads the list back from GitHub and says what happened, such as “sam now has all_repo_write.” These need an owner’s sign-in with the admin:org scope.
An organization’s rulesets
An organization ruleset applies across its repositories. Choose Rulesets… on the organization’s row to open Rulesets in that organization. Each row gives its name, its enforcement and what it targets: “Protect main: Active, on branches”.
- Choosing one reads it in plain words in Details, the same sentences as a repository’s Summary page, and which repositories it covers.
- Enforcement… (
Alt+E) makes it Active (enforced), Evaluate (reports what it would have blocked, blocks nothing, a safe way to try a rule first) or Disabled. - History (
Alt+H) lists its earlier versions, with when and by whom. - Rule Insights… (
Alt+I) lists recent pushes across the organization that its rulesets passed, blocked or let through on a bypass, for the last day, week or month. - Delete… (
Alt+L) deletes it from every repository it covers. QUILL asks you to type its name exactly, because this cannot be undone.
To make an organization ruleset from repositories that each have the same one, use Promote to Organization under Across Repositories.
Repository settings from the editor
With the Workbench in use, the editor’s Rename Repository, Change Visibility, Change Default Branch and Configure Branch Protection open the repository’s sheet at the right page, and Create Repository, Fork, Commit Multiple Files and the Codespaces commands open the Workbench on the repository and run from there.
A walk-through: labelling two issues, then taking it back
This uses the practice repository (Help > Practice on
GitHub…, Ctrl+Alt+P). It changes two practice
issues and puts them back.
- In the Workbench, go to the practice repository and press
Ctrl+Shift+1for its Issues. PressF6until you reach the list. - Press
Ctrl+E, typeno:label, and press Enter. The list narrows to the issues with no label.Alt+7says the filter in words. - Press
F6to come back to the list, select the first issue, then hold Shift and press Down Arrow to select the second as well.Alt+2says how many are selected. - Press
Alt+Enter. One sheet opens, “Properties of 2 issues”.Ctrl+Tabmoves through its pages to the one with the labels. - Tab to the labels list and check “practice: question” with Space. You hear “practice: question, on”.
- Press
Ctrl+Enter. You hear the preview, “Change 2 issues: add practice: question.”, and Enter goes ahead. The results list says Done for each. Escape closes it. - Press
Ctrl+Shift+Hfor Change History. Each issue’s change is a row of its own, newest first. Escape closes it. - Back in the list, press
Ctrl+Z. The label comes off the issue changed last, and you hear what was undone. PressCtrl+Zagain for the other. - Press
Escapein the filter box to clear the filter.
To try the same without changing anything, turn on Dry Run
(Ctrl+Alt+D) before step 6: you hear what would have been
sent, and nothing is.
Learn it with a guided lesson
Help > Tutorials (Ctrl+F2) has the
GitHub lessons. For this chapter:
- Label, comment on and close an issue: one issue’s changes, on the practice repository.
- Give someone access: an access template, applied to a person, stopping at the preview so nothing is sent.