Skip to content

Configure stale-management rules and cleanup syntax #46

@saismrutiranjan18

Description

@saismrutiranjan18

Description The current stale-management.yml workflow uses the default settings for the actions/stale action.

The Problem

Aggressive Closing: Without configuration, the action will tag and close all issues older than 60 days, including important bugs or pinned issues.

Generic Messages: The default stale message is generic and doesn't guide the user on what to do.

Redundancy: The repo-token input is no longer required for this action version.

Proposed Fix

Add configuration to exempt specific labels (e.g., pinned, security).

Customize the stale/close messages to be more friendly.

Remove the redundant repo-token line.

Fix the indentation of the schedule cron job for better readability.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions