This PR adds a new GitHub workflow combination that automatically closes issues when there's no activity from the user for 10 days, addressing the need for better issue management across serpapps repositories.

What's Added

Reusable Workflow (.github/workflows/close-inactive-issues.yml)

A configurable workflow that uses actions/stale@v9 to detect and manage inactive issues:

• Detects issues with configurable days of user inactivity (default: 10 days)
• Two-phase approach: marks as stale first, then closes after warning period
• Smart exemptions for important issues (pinned, security, under-investigation, etc.)
• Only affects issues, not pull requests
• Removes stale label when users respond

Workflow Template (workflow-templates/call-close-inactive-issues.yml)

A ready-to-use template that other repositories can adopt:

• Scheduled to run daily at 2 AM UTC
• Manual trigger capability with custom parameters
• Calls the reusable workflow with serpapps-specific configuration
• User-friendly messages explaining the automation

Template Properties (workflow-templates/call-close-inactive-issues.properties.json)

Metadata file that makes the template discoverable in GitHub's workflow template UI.

Key Features

Precise User Inactivity Detection: The workflow specifically targets cases where maintainers are waiting for user response, not general issue inactivity. This ensures legitimate ongoing discussions aren't interrupted.

Configurable Parameters:

• Days before closing (default: 10)
• Custom stale and close messages
• Exempt labels list
• Close reason

Protection Mechanisms:

• Exempts issues with labels like pinned, security, waiting-for-maintainer
• Automatically removes stale label when users respond
• Rate limiting to avoid API issues

Usage

Other serpapps repositories can now easily implement automated issue management by copying the workflow template to their .github/workflows/ directory. The workflow will:

1. Run automatically every day at 2 AM UTC
2. Check for issues with 10+ days of user inactivity
3. Mark qualifying issues as stale with a helpful message
4. Close them after 1 additional day if no user response
5. Can be manually triggered with custom parameters

This follows the established serpapps pattern for reusable workflows and integrates seamlessly with existing infrastructure.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.