Skip to content

When other issues refer to a stale issue, don't mark it as stale, especially if closed as a duplicate of to-be-stale issue #1324

Description

@Mikaela

Description:

When I close an issue as a duplicate of another issue, the bot shouldn't mark the another issue as a stale.

Justification:

For example I recently closed krille-chan/fluffychat#2602 and krille-chan/fluffychat#2147 as duplicates of krille-chan/fluffychat#89 and krille-chan/fluffychat#334 and today the bot decided to start commenting that the canonical issues have had no activity and will be closed.

GitHub issues natively support marking issues as duplicates of other issues and I would hope that information is accessible to the bot and thus it could take that and when that happened into consideration before marking issues as stale, if not even the fact that canonical issues have been referred to from other issues.

Are you willing to submit a PR?

I fear I don't have the skills required for that.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature requestNew feature or request to improve the current logic

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions