mergify changes for stale PRs

[tarun-etikala]

Provide a short summary in the Title above. Examples of good PR titles:

• "Feature: add so-and-so models"
• "Fix: deduplicate such-and-such"
• "Update: dbt version 0.13.0"

Usecase - iLab Knowledge Pipeline

Description

Give a more detailed description of your changes here. Include any motivation and context.

Fixes # (issue)

• Fixed the bug for importing path for ai-tools library in the notebooks
• Resolved dependency issues for the libraries used in the notebooks

Related Tickets

Related jira tickets here:

• 🎫 ISSUE-1242

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• [ x ] New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details for your
test configuration

• Test A
• Test B

Test Configuration:

• Python version:
• Pyspark version:
• MySQL version:
• Docker version:

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

• Chores
  • Implemented automated stale pull request management: pull requests are marked stale after 60 days of inactivity, automatically closed after 90 days without updates, and the stale label is removed when activity resumes.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds three new mergify rules to automate stale pull request management: labeling inactive PRs after 60 days, closing them after 90 days with a message, and removing the stale label when activity resumes.

Changes

Cohort / File(s)	Summary
Stale PR Lifecycle Management \.github/mergify\.yml	Added three conditional rules: mark PRs stale after 60 days of inactivity (excluding WIP/blocked/do-not-close), close stale PRs after 90 days, and remove stale label on activity. 48 lines added.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 The PR waits in silence, sixty days grow long,
A stale tag appears—"time to move along!"
Ninety sunsets pass, the door gently closes,
But whisper with activity, and up the label goes-es!
Mergify's gentle hand keeps the garden tidy, 🌿

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'mergify changes for stale PRs' accurately reflects the main change in the pull request, which adds three new mergify rules for handling stale pull requests.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/mergify.yml:
- Around line 89-96: The "remove stale label when PR has activity" rule removes
the stale label immediately because it lacks a time-based activity check; update
the rule's conditions (for the rule named "remove stale label when PR has
activity" that currently checks label=stale and -closed) to include a
recent-activity condition that only fires when the PR has had activity within
the last 60 days so the rule won't trigger immediately after the "mark as stale"
comment; keep the existing label removal action for 'stale' but add the
time-based condition to the conditions list to ensure proper delay.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Rule will immediately undo the stale label due to missing activity check.

This rule triggers whenever a PR has the stale label and is not closed. However, when the "mark as stale" rule fires, the comment it posts counts as activity, and this rule's conditions become satisfied immediately after. The result: the stale label gets added and then instantly removed.

Add a time-based condition to ensure the rule only fires when there's been recent activity (i.e., within the last 60 days):

🐛 Proposed fix

   - name: remove stale label when PR has activity
     conditions:
       - label=stale
+      - updated-at>=60 days ago
       - -closed
     actions:
       label:
         remove:
           - stale

🤖 Prompt for AI Agents

In @.github/mergify.yml around lines 89 - 96, The "remove stale label when PR
has activity" rule removes the stale label immediately because it lacks a
time-based activity check; update the rule's conditions (for the rule named
"remove stale label when PR has activity" that currently checks label=stale and
-closed) to include a recent-activity condition that only fires when the PR has
had activity within the last 60 days so the rule won't trigger immediately after
the "mark as stale" comment; keep the existing label removal action for 'stale'
but add the time-based condition to the conditions list to ensure proper delay.