Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Close stale PRs #75963

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Close stale PRs #75963

wants to merge 3 commits into from

Conversation

arunchndr
Copy link
Member

No description provided.

@arunchndr arunchndr requested a review from a team as a code owner November 18, 2024 22:34
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 18, 2024
- not:
isDraft
- noActivitySince:
days: 14
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd propose a bit longer than 14 days, since that's probably going to auto-close all our PRs that get opened around Christmas/New Years. 😄

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to give them a nudge after 2 weeks, then a bit more time to respond before closing?

- noActivitySince:
days: 14
actions:
- closePullRequest
Copy link
Member

@jasonmalinowski jasonmalinowski Nov 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we have this switch things back to draft instead? Or label the PRs closed this way? My concern being if somebody is out for a bit, it'll be harder for them to figure out which things got auto-closed when they come back.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to exempt the Roslyn team?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. Let's just move to closed after a month. If you're out a month, you should figure out what to do with your open PRs anyways.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would not exempt the team. We're both a large source of this already, and we should be able to complete things within a month, or take them out if we're making no progress on them.

Copy link
Contributor

1 file(s) have code issues.

File Issues
.github/policies/resourceManagement.yml Exception during deserialization. Unknown condition specified.

Total execution time: 0.01 seconds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants