Start a timer from GitHub issues and pull requests
Which pages are recognised
Open a single issue or pull request on github.com and the Keepr extension shows an “On this page” card above the timer. A pull request is recognised on every one of its tabs — conversation, commits, checks and files changed.
GitHub Enterprise Server works the same way, on your company's own address. Because any website can have addresses shaped like a GitHub issue, Keepr only accepts an Enterprise page once its tab title has the GitHub form “Title · Issue #12 · owner/repo”; until the page has finished loading, the card may take a moment to appear.
Lists of issues or pull requests, discussions, code and settings pages are not recognised, and neither are GitHub Projects boards yet. The extension needs no extra permission for any of this. It reads the address and title of the tab you open it on and, only when the title lacks the name, that one issue's or pull request's title (see “What the card fills in”).
What the card fills in
Press “Use” on the card. The timer description becomes the number and title, for example “#12 Fix the login redirect”, so your entries read the same as the issue. For a pull request, GitHub's “by author” suffix is left out of the title.
If a Keepr task for that issue already exists, the card says so and Use fills its project and task too. Otherwise the card names the project the new task would go into, and you can change it in the composer before pressing “Start timer”.
The title normally comes from the tab title. When the tab does not carry it yet, Keepr asks GitHub for that one issue's title from within the page, and falls back to the heading on the page — useful for private repositories, which GitHub's public API does not answer.
How the task is matched or created
Keepr stores the issue number on the task together with the issue's address. The number alone is not enough — every repository has its own #12 — so a task matches only when both the number and the repository agree. Issues and pull requests share one numbering in a repository, so #12 is always the same work whichever of the two it is.
With no matching task, Keepr guesses the project, strongest first: the project that already holds most tasks from the same repository, the project you last started that repository in from this browser, then a Keepr project named exactly like the repository.
The task itself is created only when you press “Start timer”, named after the issue title, so opening the card and walking away leaves nothing behind. Starting on the same issue next week reuses that task instead of creating a duplicate.
What you need
The extension connects with a personal API token, which is part of the Ultimate plan. Give it the timers and projects scopes; creating a task from a page also needs the projects write scope and the right to manage the chosen project. Without either, the timer still starts, on the description alone.
In the pinned side panel, Keepr follows the issue you have open once you let it read tab addresses. If you prefer not to, allow just your GitHub site when the panel offers it, or add your Enterprise address under Options.