SpecForge v0.25.0
The pull requests that ship your changes now sit beside them. An opt-in panel lists the open BitBucket pull requests you authored, with their review state, in whichever corner of the side panes you choose.
✨ Highlights
- Your BitBucket pull requests in the sidebar. A new panel lists the open pull requests you authored across every BitBucket Cloud workspace your account belongs to, most recently updated first. Each row shows the repository, the title, the source and destination branches, a review summary — approvals (your own excluded), changes requested, and reviewers who have not responded yet — the open-task count, a draft marker and when it was last updated. Activating a row opens the pull request on BitBucket: in your browser from the desktop app, in a new tab from the browser skin. The list refreshes every two minutes in the background. If BitBucket is briefly unreachable the last list stays up, dimmed as stale, instead of vanishing; missing or under-scoped credentials, an outage and an empty list each get one quiet line of their own. The panel is read-only: nothing is approved, merged or commented on from SpecForge.
- Put the panel where it suits you. Settings offers four slots — the top or bottom of the left or right side pane — and defaults to the bottom of the left pane, between the workspace tree and the Archive entry. The choice persists across restarts, applies to the desktop app and the browser skin alike, and moves the panel in windows that are already open. A panel in a side pane hides and shows with that pane, and its height is capped so the sidebar footer and the usage-quota strips never scroll out of reach.
- Off by default, with a token that never comes back out. Nothing is read
or sent until you switch on Settings ▸ BitBucket pull requests and save a
username (or Atlassian account email) and a BitBucket API token with read
access to Account, Workspace membership and Pull requests. A Jira or
Confluence token is not accepted — BitBucket Cloud needs its own. The token
is stored with your other settings, is only ever sent to
api.bitbucket.org, and no command on any frontend returns it: Settings shows only whether one is set, so a browser skin reachable over your network cannot read it back. For a headlessspecforge-serve, set bothBITBUCKET_USERNAMEandBITBUCKET_API_TOKENin its environment and they take precedence over the stored pair. An older SpecForge ignores these settings and drops them the next time it saves any setting.
🔧 Improvements
- The terminal UI gets the switch. The
specforge-tuiSettings screen gains a third toggle for BitBucket pull requests, so the opt-in can be flipped from the terminal. The terminal does not show the list itself.