Eleven open pull requests, sorted by what is actually ready

What is the review backlog pass doing?

Listing open pull requests across the repositories you care about, with age, author and reviewer state, and flagging the ones nobody has looked at. Two facts per row and the whole thing fits in a message. It stops a fix sitting unreviewed for six weeks because it was opened during a release.

The version that earns its keep goes further. A companion opens the linked issue, checks whether the branch still merges cleanly, sees whether the pipeline passed, and says which of the eleven are ready. That is the judgement a reviewer makes in thirty seconds, done in advance for all of them.

Spot the test that keeps failing

Bitbucket Pipelines fails for ordinary reasons: a flaky test, an expired credential, a base image that moved. What separates a team that fixes those quickly from one that stops trusting CI is whether anybody notices the pattern. Three red builds on the same test in a week is a pattern.

The Available tools section on the Bitbucket entry under `strawberry://settings/integrations` lists every tool the connection exposes and marks the read-only ones. Keep anything that triggers a pipeline or merges a pull request at Ask every time in the Permissions block. Pairing this with Jira makes the blocked-review question answerable in one pass.

• Open pull requests with age, author and reviewer state.
• Pipeline results, and whether the same test is failing repeatedly.
• Merges and pipeline triggers: consequential, so keep them behind an approval.
• An account or app password scoped to the specific repositories rather than the whole workspace.

Why does the browser half matter for a code host?

Because the code is half of any engineering question.

Why a branch stalled is usually in a ticket, a design review, or a conversation where somebody said "let’s wait for the migration" and nobody wrote it down. A companion reading Bitbucket plus your signed-in tracker assembles the whole story.

The recurring form is a weekly engineering rollup: what shipped, what is blocked, which reviews are waiting on whom. By hand it costs a lead an hour every Friday, which is why it happens for three weeks after somebody asks for it. Release notes falls out of the same data.

Frequently asked questions