Starting the board
Loading the board's code
Connect it, once
This page has no server. It talks to GitHub straight from your browser, with a token you make yourself. Your half of the board, the notes and the colours, is saved in this browser, and in your own private repository once you set up cloud storage in Settings.
-
Create a fine-grained token
GitHub's form asks you four things. Here is the answer to each one.
-
Paste the token here
GitHub shows it once, when you create it. Copy it before you leave that page.
Set this board up before, in another browser? Paste the backup you copied from its Settings here instead, and skip every step above.
The token stays in this browser and is sent only to GitHub. Anything else with access to this browser can read it, so keep it scoped to the repositories you need and give it an expiry date.
Waiting for you
Pull requests waiting for your review
0Assignee
No review waiting for you matches the assignee filter.
Your issues and pull requests
Kind
Repository
Reviewer
Label
If your work lives in an organisation, add a token owned by that organisation. One token reaches one owner and never a second.
Settings
Tokens that read your work
These tokens fetch your issues and pull requests. Each one reaches one owner, your account or one organisation. Opening this screen tries every permission the board needs on every token, and each one says what it could do and what to add if it could not. They save nothing: saving is the next card's job.
A backup is one piece of text holding every token and the name you gave it. Keep it in your password manager. To set this board up in another browser, on another computer, or in another Chrome profile, press Add token there and paste that text instead of a token.
Cloud storage: where your half of the board is saved
Your notes, the cards you moved by hand, and how the board looks are saved in this browser, and in your own private repository once cloud storage is set up. One storage token does the saving, and the same cloud storage serves every project on this site.
Suggested cleanup
A note stays in your data repository after its issue closes or its pull request merges. This lists those notes, so you can delete them or keep them.
How the board looks
Saved beside your notes, so the board looks the same on every machine you open it on.
Theme
Colour on each part of the board, and whether it is shown
What the tab name counts
The browser tab is named "Work Board", with the number of things waiting on you in brackets. Choose which parts of the board add up to it, and whether each part counts the work you marked "not a priority". That second answer also changes the number on that part's own badge. A part that you hid from the board never adds to it.
Lines you copy from a card
Write a line once here, and copy it filled in from any card's menu. The board puts the card's own number, link or title where you left a placeholder. Saved beside your notes, so your lines are there on every machine you open the board on.
You have written none yet. For example:
A new line
The name is what the card's menu shows. The line below it is what you get.
What you can put in a line
Something wrong, or an idea?
Tell me on GitHub. The form opens with this board already named, so you only say what happened. You need a GitHub account, and the report is public.
Add a token
A token is how this page proves to GitHub that it may read your work. You make it yourself, it stays in this browser, and it is sent to GitHub and nowhere else.
Already have a backup?
If you set this board up in another browser, you do not need a new token. Copy the backup from that board's Settings and paste it into step 4 below. Every token comes back, with its name.
-
Decide whose work this token is for
A token reaches one owner: your own account, or one organisation. It can never see the other, whatever permissions you give it. So a person whose work lives in an organisation and in their own account needs one token for each.
-
Fill in GitHub's form
GitHub's form asks you four things. Here is the answer to each one.
An organisation's owner may have to approve the token before it works. Until they do, the board sees nothing through it and says so.
-
Copy the token
GitHub shows the token once, on the screen that creates it, and never again. Copy it before you leave that page. If you lose it, you cannot read it back anywhere: you have to make another one.
-
Paste it here
GitHub does not say which owner a token belongs to, so the board cannot name it for you. Leave this empty and it suggests a name from wherever the token finds work. You can rename it in Settings at any time.
The token stays in this browser and is sent only to GitHub. Anything else with access to this browser can read it, so keep it scoped to the repositories you need and give it an expiry date.
Suggested cleanup
These notes are on issues that closed and pull requests that merged or closed. The board never shows those cards again, so the notes stay in your data repository and nobody reads them. Delete what you no longer need. Choose "Keep" for a note you want, and the board stops suggesting it, on every device.
A deleted note is not lost for good. Your data repository keeps every saved version in its history, so you can still read it on GitHub.