Conversation
Extracted logic for determining last activity and updating issue staleness into separate functions `determine_last_activity` and `update_issue_staleness`. This simplifies the main `check_stale_issues` function and makes the logic more testable and maintainable. The refactoring preserves the existing logic, including optimizations to skip note fetching if the issue is already stale by its update date. Verified with existing unit tests in `src/tests/polling_tests.rs`. 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. |
1 participant
Refactored
check_stale_issuesinsrc/polling.rsto improve readability and maintainability.process_issue_staleness,determine_last_activity, andupdate_issue_stalenesshelper functions.check_stale_issuesto use these helpers within the async stream processing.PR created automatically by Jules for task 14554400180212362396 started by @myaple