labels: PR list and cross-repo search pass labels= by name — org-label filters silently no-op on Gitea (follow-up to #12) #64
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#64
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?
#12 fixed org-label name resolution and switched the issue-list
labels=filter to numeric IDs, because Gitea's per-repo by-name filter is org-label-blind and fails open (returns the full unfiltered list). Two label-filter paths still pass raw NAMES upstream (found during #12's adversarial review, explicitly scoped out by the builder):internal/service/pr.go:94—ListPRspassesopts.Labelsas names to the per-repo pulls list endpoint. Filtering PRs by an org-label name on Gitea silently returns ALL PRs unfiltered.internal/service/issue_search.go:19— cross-repoSearchIssuespasses label names. (Upstream uses the name-globalGetLabelIDsByNameshere, so behavior differs from the per-repo case — verify what org labels do before choosing IDs vs client-side filtering.)Acceptance
Refs #12.