feat: add repo-level filter to issues and pulls list views #86
Reference in New Issue
Block a user
Delete Branch "feature/repo-filter-83"
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?
Summary
ListAllIssuesandListAllPullRequestsavoids unnecessary API callsCloses #83
Changed files
internal/gitea/client.go-- AddedrepoFilterparameter toListAllIssuesandListAllPullRequestsinternal/handlers/handlers.go-- Readrepoquery param, populateReposlist from selected org, pass filter to clientinternal/templates/issues.html-- Added repo dropdown, updated scroll sentinel and hx-includeinternal/templates/pulls.html-- Same changes as issues templateTest plan
Generated with Claude Code
Review: APPROVED
Smart approach to filter at the repo list level before fanning out API calls. Conditional repo dropdown (only shown when org is selected) is the right UX. Cache keys properly updated.
This will conflict with PR #85 (label filter) -- both modify the same function signatures. Recommend merging #84 first, then #85, then rebasing this PR to incorporate both parameters. Will handle the merge order accordingly.
ed638f52ceto6033278a86