Abhinandankaushik opened a new issue, #150:
URL: https://github.com/apache/datafusion-site/issues/150

   ### Description:
   
   Currently, the repository does not have any automated mechanism to manage 
inactive (stale) issues and pull requests. As a result, many old issues and PRs 
remain open indefinitely, even when they are no longer relevant or actively 
being worked on. This leads to:
   
   - Cluttered issue tracker
   - Increased maintenance overhead
   - Difficulty in identifying active vs inactive work
   - Slower triaging process for maintainers
   
   To improve repository hygiene and reduce manual effort, we propose adding an 
automated Stale Issue Bot using GitHub Actions.
   
   
   ### Proposed Solution:
   
   We propose implementing a Stale Issue Bot using the actions/stale GitHub 
Action. The bot will automatically monitor issues and pull requests and take 
the following actions:
   
   ✅ Behavior of the bot
   
   1. If an issue or PR has been inactive for 60 days:
      - The bot will post a comment notifying that it has become stale.
      - The bot will add a stale label to the issue/PR.
   2. If there is no activity for 7 more days after marking it stale:
      - The bot will automatically close the issue or PR.
   
   **Proposed Implementation :**
   A new workflow file should be added:
   ```
   .github/workflows/stale-bot.yml
   ```
   
   **Expected Benefits:**
   
   This automation will:
   
   - Keep the repository clean and organized
   - Reduce manual effort for maintainers
   - Help prioritize active issues and PRs
   - Prevent outdated discussions from lingering indefinitely


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to