"See #482." Issue and pull request numbers come up in every stand-up, chat thread and commit message, and a bare number does not say which repository it belongs to. Opening one means finding the repository, then the Issues tab, then typing the number. A Wyrd keyword for each repository you work in turns that into one line.
Short answer. Save your repository's issue address (step 2 below makes it for you) under the keyword issue. Then type > issue 482 in the address bar and press Enter. Or select a number on any page, right-click it and choose Wyrd search.
See it work
Two ways in: type the number, or right-click it where you found it. Try both.
Typed in Chrome's address bar: >, a space, the keyword issue and the number. Press Enter.
The number is selected in the team chat, open in Chrome. Right-click, then pick the search.
#482 · Checkout test fails on CI
Set it up
Two minutes, once. Keywords and right-click search work from the moment Wyrd is installed, with no account.
- Add Wyrd from the Chrome Web Store.
- Type your repository as
owner/name, or paste the address of any page in it. The addresses on this page change to yours.That does not look like a repository yet. It should look like owner/repo or github.com/owner/repo.
Your keyword's address:
https://github.com/owner/repo/issues/%sAdd to WyrdNew in 1.2Add to Wyrd does this and the next step for you: Wyrd's Add box opens with the keyword and the address filled in. Check them and press Add; nothing is saved until you do.
- Click Wyrd's icon in Chrome's toolbar. Paste the address into Address, type
issuein Keyword and click Save. - In the address bar, type
>, press Space, thenissueand an issue or pull request number, and press Enter.
Whatever you type after issue goes where the address says %s. A pull request number works too: GitHub sends /issues/482 on to the pull request when 482 is one. Typed on its own, > issue opens the repository's issues.
Several repositories
Give each repository its own keyword, named after it: > shop 482, > api 77. Or one keyword for the whole organisation, with numbered blanks: save https://github.com/acme/%1/issues/%2 as acme, then type > acme shop 482. The words fill the blanks in order.
Right-click a number where you read it
In a chat, an email, a document or a pull request open in Chrome, select the number (just 482, without the #), right-click, choose Wyrd search: "482" and then issue. It opens in a new tab next to the one you are reading.
- The menu lists your three most-used search keywords, so
issuejoins it once you use it more than the others. - To keep your repositories there from day one, under names like Shop issue and API issue: open Wyrd's Features page (Settings → Features), switch on Your right-click searches and pick them, up to 12. It needs no permission.
- It works on web pages in Chrome, such as Slack or Gmail in a tab. Desktop apps outside Chrome have their own menus.
More GitHub keywords
| Keyword | Address | You type | Opens |
|---|---|---|---|
issue | https://github.com/owner/repo/issues/%s Add | > issue 482 | An issue, or a pull request, by its number |
pr | https://github.com/owner/repo/pull/%s Add | > pr 497 | A pull request by its number |
issues | https://github.com/owner/repo/issues?q=%s Add | > issues is:open label:bug | The repository's issues and pull requests, searched with GitHub's own search words |
commit | https://github.com/owner/repo/commit/%s Add | > commit a5c3785 | A commit by its hash |
board | Your project's address | > board | A project board or a saved search: open it, click Wyrd's icon and save it as it is |
A keyword is yours to name: if you only ever work in one repository, i is quicker to type than issue.
Give the whole team the same keywords
One person keeps the team's keywords in a Google Sheet (or a file in a GitHub repository) and everyone subscribes once in Wyrd: a keyword for each repository, the CI dashboard, the on-call rota, the runbooks. A new engineer has them on day one, and when a repository moves, one row changes. Each person's own keywords always win over the list's, so nobody loses theirs. Free for teams of up to 30 people; larger teams, see pricing.
How: share links with your team, or start from the small team template.
If it does not work
- GitHub shows "404". The repository is private and you are signed out, or the number is in another repository. Sign in to GitHub once in Chrome, and check which repository the keyword points at.
- The repository's issues open instead of the one you asked for. The address is missing
%s. Copy it again from step 2. - Google searches for "issue …". The
>and the space were missing, or Wyrd is switched off inchrome://extensions. - The right-click menu has no
issue. It is not among your three most-used searches yet: switch on Your right-click searches (above). - "This site can't be reached" or "Server Not Found" at wyrd.internal. That address only works inside Wyrd: Wyrd is not installed in this browser, or needs an update. Add it from the Chrome Web Store, then try again.
Next steps
- Guides for Jira, Azure DevOps, ServiceNow and Zendesk: with the tools you use.
- Give your team its list: share links with your team.
- Every command and what it needs: the cheat sheet.
GitHub is a trademark of GitHub, Inc. Wyrd is an independent extension, not made by or affiliated with GitHub. Wyrd reads nothing from GitHub: it only opens the address you saved.
NextOpen Azure DevOps work items →