We have isssues on the side bar so the next logical step is to have PR's. Maybe tabs on top with the count? #39
Labels
No labels
bug
docs
enhancement
good first issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pedromcaraujo/forge#39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Design: PRs in the drawer via tabs
Decided direction: tabs (Issues | PRs) inside the same forgejo panel, each with an open-count. The PR list reuses the existing accordion machinery. A standalone "linked PR inside issue detail" view is a possible later add-on, not v1.
Scope
Sidecar (
web/panel.py)GET /panel/<ch>/pulls→ open PRs via/repos/{repo}/pulls?state=open, returningnumber, title, labels, draft(mirrorslist_issues).GET /panel/<ch>/pulls/<n>→ detail, same markdown-render + URL-rewrite path asissue_detail, plusbase/headandmergeable. Comments/attachments already work (PRs share the issue index).can_createstays issues-only (quick-add is an issues affordance).Module (
modules/forge.nix+launcher.nix)typeenumforgejo-issues→forgejo, keepingforgejo-issuesas an accepted alias so existing channel configs don't break. The panel now means "issues + PRs".Frontend (
web/index.html)renderForgejoIssues→renderForgejo: a tab strip (Issues / PRs, each with a count chip) above the accordion; registry maps bothforgejoandforgejo-issuesto it.issueRowwith a state marker + PR-flavored inject text.localStorage.Defaults for v1
/commits/{sha}/statuscall; keeps v1 at two endpoints). Follow-up.look at PR #N: <title>(a bare#Nis ambiguous to a human).