The quick answer

Attach a public GitHub repository to a Whiskrs project, optionally enter a GitHub username, and load Repository pulse. It shows recent open PRs, issues assigned to that username and checks for the default branch’s latest commit, with manual refresh and clear unavailable states.

Start with the project destinations

A repository is only one part of a developer’s working context. Keep its documentation, local server and issue tracker in the same project launcher. You can open those destinations together rather than rebuilding a set of tabs at the beginning of each session.

In Whiskrs’s Your Space, create a project and add a repository link. Set up Repository pulse beside it. The repository field can be prefilled from a GitHub URL, while a saved GitHub profile can supply a username for assigned issues. Review both values before loading activity.

Read each signal in its own context

Open pull requests show work proposed for the repository, including draft labels. Assigned issues use the username you enter; they are not an authenticated view of every task you can access. “View all” opens GitHub when you need the full list.

CI is associated with a commit. Whiskrs pins checks and legacy status results to the latest commit it reads from the default branch and displays the commit SHA. This is different from a particular pull request’s head commit. A passing default-branch check does not prove that every proposed change passes.

Refresh when you need an update

Repository pulse refreshes on request and uses a short in-memory cache. It does not continuously poll GitHub in the background. After a browser or service-worker restart, refresh again to load a current reading.

Public activity does not require a GitHub OAuth app or sign-in in this release. Chrome requests the relevant optional GitHub API access when the feature is enabled. Private repositories and GitHub Enterprise are outside v1’s pulse support. Do not treat the absence of a private result as an empty queue.

Handle unavailable activity as unavailable

A rate limit, network failure or incomplete checks response should not turn into a healthy green status. Whiskrs labels failed or missing reads and distinguishes a previous reading from a successful current one. Wait for the displayed reset when limited, then refresh.

Use the pulse as a convenient starting point beside your saved references. Open GitHub for reviews, approvals, detailed check logs and the complete issue list. When the integration is no longer relevant, remove the pulse without deleting the project or its saved destinations.

Put it into practice

Keep repository activity close to your working links, while checking the repository, assignee and commit behind each status.

See the Whiskrs help guide for current setup details, or read the privacy policy for data handling and optional integrations.

Add to Chrome