DOCSEARCHbyAlgolia
Submit Docs

Sonia Stale Action

website·Indexed 29 days ago

https://sonia-corporation.github.io/stale/

A GitHub Action designed to help maintainers manage stale items in their repositories. It provides automated workflows for marking issues and pull requests as stale, closing them after a period of inactivity, and managing related labels and branches.

Tokens
47.2K
Snippets
284
Records
487
Agent score
67%

What's inside Sonia Stale Action

  1. Overview of the Stale GitHub Action

    The Stale GitHub Action helps repository maintainers manage inactive open issues and pull requests. It identifies 'stale' items based on inactivity and can automatically flag them with labels or close them to reduce maintenance overhead.

  2. Overview of the stale GitHub Action

    The stale GitHub Action helps repository maintainers manage inactive open issues and pull requests. It automates the process of 'flagging' inactive items as stale and closing them if they remain inactive, reducing the manual overhead of repository maintenance.

  4. Understand stale action annotations on the Summary page

    After the stale action completes, it may display annotations on the GitHub Action Summary page to provide feedback on the workflow execution. These are categorized into three types:

    1. Notices (ℹ️): Provide an overview of the workflow, specifically counts for the number of issues and pull requests processed. These are derived from the action's statistics and outputs.
    2. Warnings (⚠️): Currently used to notify users about missing features. Users are encouraged to open a ticket if they encounter these.
    3. Errors (❌): Indicate failures typically caused by incorrect action configuration, misconfigured repository labels, or rare GitHub API HTTP errors. If a bug is encountered, it should be reported via a bug ticket.

  5. Analyze workflow behavior using statistics

    To get an overview of the workflow's execution, review the logs. At the end of the run, the workflow provides a list of statistics detailing the main events that occurred, such as the number of processed, ignored, and unaltered issues and pull requests. These statistics can also be retrieved via annotations.
    Issues statistics
├── Processed issues 28
├── Ignored issues   3
└── Unaltered issues 25
Pull requests statistics
├── Processed pull requests 5
└── Ignored pull requests   5

  10. Understand stale action annotations on the Summary page

    After the stale action completes, it may display annotations on the GitHub Summary page to provide feedback on the workflow execution. These annotations are categorized into three types:

    • Notices (ℹ️): Provide an overview of the workflow, specifically counts for the issues and pull requests processed. These are derived from the action's statistics and outputs.
    • Warnings (⚠️): Currently used to indicate missing features. Users are encouraged to open a ticket to request these features.
    • Errors (❌): Typically indicate misconfiguration of the action or repository labels. They may also result from GitHub API HTTP errors or general bugs.