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

chore: bring back needs info workflow #10293

Merged
merged 1 commit into from
Oct 25, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 0 additions & 16 deletions .github/no-response.yml

This file was deleted.

58 changes: 0 additions & 58 deletions .github/stale.yml

This file was deleted.

33 changes: 33 additions & 0 deletions .github/workflows/stale.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# SPDX-FileCopyrightText: 2019 Nextcloud GmbH and Nextcloud contributors
# SPDX-License-Identifier: MIT
name: Close stale issues

on:
workflow_dispatch:
schedule:
- cron: "0 0 * * *"

jobs:
stale:
runs-on: ubuntu-latest

if: ${{ github.repository_owner != 'nextcloud-gmbh' }}

permissions:
issues: write

steps:
- uses: actions/stale@v9
with:
repo-token: ${{ secrets.COMMAND_BOT_PAT }}
stale-issue-message: >
Hi there! It looks like this issue hasn’t seen much activity for a while and might need a bit more information to move forward.
If we don’t hear back soon, we may close it to keep things organized.
Thanks again for your contributions – we really appreciate it!
stale-issue-label: 'stale'
only-labels: 'needs info'
exempt-issue-labels: '1. to develop,2. developing,3. to review,4. to release,discussion'
days-before-stale: 30
Copy link
Member

Choose a reason for hiding this comment

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

Let's go higher or the action might tag too many tickets as stale in the next few days. Our issue tracker is still not fully triaged.

How about 90?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Let's go higher or the action might tag too many tickets as stale in the next few days. Our issue tracker is still not fully triaged.

I think that's fine because the stale action will only comment on issues with the needs info label. Everything else is ignored.

days-before-close: 14
debug-only: ${{ vars.WORKFLOW_STALE_DEBUG_ONLY == 'yes' }}

Loading