Refactor check_stale_issues for better readability#80
Conversation
Extracted logic for determining last activity and managing stale labels into separate helper functions: `determine_last_activity` and `manage_stale_label`. This simplifies the main `check_stale_issues` function and makes the code more modular and testable, while preserving the existing behavior and parallel processing structure. 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. |
Refactored
check_stale_issuesinsrc/polling.rsto improve code health.determine_last_activityto handle timestamp calculation and note fetching logic.manage_stale_labelto handle the side effects of updating issue labels.check_stale_issuesloop.src/tests/polling_tests.rs.PR created automatically by Jules for task 750441959531310367 started by @myaple