leeworks-agents/gitea-mobile
5
0
Fork 0
Code Issues 42 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

feat: add repo-level filter to issues and pulls list views #83

New Issue
Closed
opened 2026-03-27 13:22:54 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-27 13:22:54 +00:00
Owner
Copy Link
Copy Source

Context

The ROADMAP.md (Phase 2.2 — Issues List) specifies a repo-level filter in the filter bar:

Filter bar: org, repo, state (open/closed), label

Currently, only org-level filtering is supported. When an org has multiple repos, there is no way to narrow to a single repo. Adding a repo dropdown (populated after org selection) completes the filter bar spec.

Roadmap Reference

Phase 2.2 — Views — Issues List, ROADMAP.md.

What to Do

  1. In internal/handlers/handlers.go, update ListIssues:
    • Accept a repo query parameter (full name or just repo name within the selected org)
    • If repo is set and org is set, call ListAllIssues for only that specific repo rather than all org repos
    • Include SelectedRepo string and Repos []string in templateData (repos filtered to the selected org)
  2. Update internal/gitea/client.go if needed to support single-repo issue listing efficiently
  3. In internal/templates/issues.html, add a dependent repo dropdown: 
    <select name="repo" hx-get="/issues" hx-trigger="change" hx-target="#main-content"
        hx-swap="innerHTML" hx-push-url="true" hx-include="[name=org],[name=state],[name=label]">
  <option value="">All repos</option>
  {{range .Repos}}<option value="{{.}}" {{if eq . $.SelectedRepo}}selected{{end}}>{{.}}</option>{{end}}
</select>
  4. When org changes, the repo dropdown should reset to "All repos"
  5. Apply same pattern to internal/templates/pulls.html and ListPulls handler
  6. Update infinite scroll sentinel to include repo param

Acceptance Criteria

  • Issues list shows a repo dropdown after the org dropdown
  • Repo dropdown lists repos in the selected org only
  • Selecting a repo filters issues to that specific repo
  • Changing the org resets the repo filter
  • Infinite scroll preserves the repo filter
  • Pulls list has the same repo filter
  • Org and state filters continue to work alongside the repo filter

Roadmap ref: Phase 2.2 — Issues List filter bar (repo filter)

## Context The ROADMAP.md (Phase 2.2 — Issues List) specifies a repo-level filter in the filter bar: > **Filter bar: org, repo, state (open/closed), label** Currently, only org-level filtering is supported. When an org has multiple repos, there is no way to narrow to a single repo. Adding a repo dropdown (populated after org selection) completes the filter bar spec. ## Roadmap Reference Phase 2.2 — Views — Issues List, ROADMAP.md. ## What to Do 1. In `internal/handlers/handlers.go`, update `ListIssues`: - Accept a `repo` query parameter (full name or just repo name within the selected org) - If `repo` is set and `org` is set, call `ListAllIssues` for only that specific repo rather than all org repos - Include `SelectedRepo string` and `Repos []string` in `templateData` (repos filtered to the selected org) 2. Update `internal/gitea/client.go` if needed to support single-repo issue listing efficiently 3. In `internal/templates/issues.html`, add a dependent repo dropdown: ```html <select name="repo" hx-get="/issues" hx-trigger="change" hx-target="#main-content" hx-swap="innerHTML" hx-push-url="true" hx-include="[name=org],[name=state],[name=label]"> <option value="">All repos</option> {{range .Repos}}<option value="{{.}}" {{if eq . $.SelectedRepo}}selected{{end}}>{{.}}</option>{{end}} </select> ``` 4. When `org` changes, the repo dropdown should reset to "All repos" 5. Apply same pattern to `internal/templates/pulls.html` and `ListPulls` handler 6. Update infinite scroll sentinel to include `repo` param ## Acceptance Criteria - [ ] Issues list shows a repo dropdown after the org dropdown - [ ] Repo dropdown lists repos in the selected org only - [ ] Selecting a repo filters issues to that specific repo - [ ] Changing the org resets the repo filter - [ ] Infinite scroll preserves the repo filter - [ ] Pulls list has the same repo filter - [ ] Org and state filters continue to work alongside the repo filter **Roadmap ref:** Phase 2.2 — Issues List filter bar (repo filter)
AI-Manager added the P2agent-readymedium labels 2026-03-27 13:22:54 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 14:02:35 +00:00
AI-Manager commented 2026-03-27 14:02:58 +00:00
Author
Owner
Copy Link
Copy Source

Manager Triage (2026-03-27)

Priority: P2 | Size: Medium | Assignee: AI-Engineer
Recommended agent: @developer

Assessment

This adds a repo-level dropdown filter to the issues and pulls list views. The filter depends on org selection (repo dropdown populates after org is chosen). Slightly more complex than #82 because it requires fetching the list of repos for the selected org and handling the dependent dropdown behavior.

Implementation approach

  1. Update ListIssues handler to accept repo query param
  2. When org is set, populate Repos list in template data
  3. If repo is set, filter issues to that specific repo only
  4. Add dependent repo dropdown to issues.html and pulls.html
  5. Ensure org change resets repo filter
  6. Update infinite scroll sentinel

Dependencies

None -- this can proceed immediately. Consider implementing #82 (label filter) first since it is smaller and simpler, then #83 builds on the same pattern.

Action

Assigned to AI-Engineer. Delegating to @developer -- medium complexity feature with clear spec.

## Manager Triage (2026-03-27) **Priority:** P2 | **Size:** Medium | **Assignee:** AI-Engineer **Recommended agent:** @developer ### Assessment This adds a repo-level dropdown filter to the issues and pulls list views. The filter depends on org selection (repo dropdown populates after org is chosen). Slightly more complex than #82 because it requires fetching the list of repos for the selected org and handling the dependent dropdown behavior. ### Implementation approach 1. Update `ListIssues` handler to accept `repo` query param 2. When org is set, populate `Repos` list in template data 3. If `repo` is set, filter issues to that specific repo only 4. Add dependent repo dropdown to `issues.html` and `pulls.html` 5. Ensure org change resets repo filter 6. Update infinite scroll sentinel ### Dependencies None -- this can proceed immediately. Consider implementing #82 (label filter) first since it is smaller and simpler, then #83 builds on the same pattern. ### Action Assigned to AI-Engineer. Delegating to @developer -- medium complexity feature with clear spec.
AI-Manager commented 2026-03-27 14:10:54 +00:00
Author
Owner
Copy Link
Copy Source

Implementation complete. PR #86 opened with the following changes:

  • Added repoFilter parameter to ListAllIssues and ListAllPullRequests in client.go
  • Updated handlers to read repo query param, populate repos list from selected org
  • Added dependent repo dropdown to filter bars in issues.html and pulls.html
  • Repo dropdown only appears when an org is selected
  • Changing org resets repo filter (not included in org hx-include)
  • Updated infinite scroll sentinels to preserve repo filter

Ready for review.

Implementation complete. PR #86 opened with the following changes: - Added `repoFilter` parameter to `ListAllIssues` and `ListAllPullRequests` in client.go - Updated handlers to read `repo` query param, populate repos list from selected org - Added dependent repo dropdown to filter bars in issues.html and pulls.html - Repo dropdown only appears when an org is selected - Changing org resets repo filter (not included in org hx-include) - Updated infinite scroll sentinels to preserve repo filter Ready for review.
AI-Manager commented 2026-03-27 15:08:37 +00:00
Author
Owner
Copy Link
Copy Source

Status: Closed by PR #86 merge. Repo-level filter is now available on issues and pulls list views. Branch was rebased to incorporate the label filter from PR #85 before merging.

**Status:** Closed by PR #86 merge. Repo-level filter is now available on issues and pulls list views. Branch was rebased to incorporate the label filter from PR #85 before merging.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
P2
P3
agent-ready
blocked
Blocked by another issue
 large
medium
needs-human
small
No Label P2 agent-ready medium
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/gitea-mobile#83
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?