feat: support API-level label filtering during sync#319
Open
hyangah wants to merge 4 commits into
Open
Conversation
Correct various klog format string errors that cause compilation failures under modern Go versions (due to automatic go vet checks). - Fix %w usage in klog.Errorf (replaced with %v). - Fix %s usage for slices and maps (replaced with %v). - Fix argument mismatches (missing or wrong type arguments). TAG=agy CONV=158419b3-c81a-4bc9-84bd-33cbf848ab3f
- Update actions/checkout to v4 (fixes Node.js deprecation issues) - Update actions/setup-python to v5 - Update actions/setup-go to v5 - Update pre-commit/action to v3.0.1 - Bump Go version to 1.25.0 in go.mod and CI TAG=agy CONV=158419b3-c81a-4bc9-84bd-33cbf848ab3f
hyangah
force-pushed
the
api-label-filtering
branch
from
June 26, 2026 01:17
d1cacbf to
41872cd
Compare
- Remove trailing whitespace on push-latest-dev-image target - Add missing newline at end of file TAG=agy CONV=158419b3-c81a-4bc9-84bd-33cbf848ab3f
This allows filtering issues by label at the API level during sync, by parsing query parameters (e.g., ?labels=foo) in the repository URL. This is useful for large repositories (like golang/go) that exceed the 10,000 issue pagination limit of the GitHub REST API, allowing users to sync only a subset of issues they care about. - Parse query parameters in parseRepo to extract labels. - Include labels in the cache key to prevent overwriting. - Pass labels to the GitHub API list options.
hyangah
force-pushed
the
api-label-filtering
branch
from
June 26, 2026 01:24
41872cd to
37972d4
Compare
Contributor
Author
Member
|
@hyangah, ready for that rebase. I'll wait to review until then so it's a clean diff. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For very large repositories (such as golang/go ), syncing all issues
can exceed the 10,000-issue pagination limit of the GitHub REST API,
or consume a prohibitive amount of API quota.
This PR introduces API-level label filtering during the repository
sync process. By allowing users to specify labels directly in the
repository URL, Triage Party can now sync only the subset of issues
they care about, bypassing scale limitations and improving sync
performance.