Conversation
Introduced `get_opened_issues` in `GitlabApiClient` to filter issues by `state=opened` via the GitLab API. Updated `poll_repository` to use `get_opened_issues` for the stale issue check, replacing the inefficient fetch-all-and-filter-client-side approach. This optimization significantly reduces the amount of data transferred and processed when checking for stale issues, especially in repositories with many closed issues. Added a test case `test_get_opened_issues` to verify the new API method sends the correct query parameters. Co-authored-by: myaple <10523487+myaple@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
myaple
deleted the
optimize-issue-polling-server-side-10649711121200368687
branch
1 participant
Optimize issue polling by filtering opened issues server-side. Added
get_opened_issuestoGitlabApiClientand used it inpoll_repositoryfor stale issue checks. Added unit test.PR created automatically by Jules for task 10649711121200368687 started by @myaple