Issue cleanup automation should close issues "As not planned" instead of "As completed"

Open
#111,131 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github
Domain
devops, tooling

Research direction

Start by locating how the dotnet-policy-service automation closes stale issues and determine whether its closure reason is configured in this repository or externally. Compare the behavior with the example issue and verify that stale issues are closed as “Not Planned” rather than “Completed”.

Written by the indexing model from the issue text.

Description

area-Meta

The issue cleanup bot, running under dotnet-policy-service, currently closes issues with the standard "Completed" (purple) reason.

Issues marked as "Completed" are meant to be used when something was done to fix/implement them, which is not the case when the closure reason was staleness.

Here is an example:

Image

I propose that the automation is changed to use the "Close as Not Planned" reason (gray) instead, to make it clearer that the issue was not implemented.

Some similar discussion here for reference:

There, it is even mentioned that "Close as Not Planned" hints as "staleness" being one of the possible underlying use cases:
Image

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.