Skip to content

Delete unused .github/stale.yml#1708

Merged
sbc100 merged 1 commit into
emscripten-core:mainfrom
mcbarton:remove-unused-stale.yml
May 11, 2026
Merged

Delete unused .github/stale.yml#1708
sbc100 merged 1 commit into
emscripten-core:mainfrom
mcbarton:remove-unused-stale.yml

Conversation

@mcbarton
Copy link
Copy Markdown
Contributor

Maybe I am wrong, but this stale.yml file doesn't appear to do anything, so this PR removes it. I could alternatively add the following Github workflow which should do what this stale.yml is trying to do (workflow could be expanded to close inactive PRs too).

name: Close inactive issues
on:
  schedule:
    - cron: "30 1 * * *" # Didn't know when best to set this cron job

jobs:
  close-issues:
    runs-on: ubuntu-latest
    permissions:
      issues: write
    steps:
      - uses: actions/stale@b5d41d4e1d5dceea10e7104786b73624c18a190f # v10.2.0
        with:
          days-before-issue-stale: 365
          days-before-issue-close: 30
          stale-issue-label: "wontfix"
          stale-issue-message: |
             This issue has been automatically marked as stale because there has been no
             activity in the past year. It will be closed automatically if no further
             activity occurs in the next 30 days. Feel free to re-open at any time if this
             issue is still relevant.
          exempt-issue-labels: 'pinned,security'
          operations-per-run: 1000 # Maximum number of issues this workflow can close in one workflow run

@sbc100
Copy link
Copy Markdown
Collaborator

sbc100 commented Apr 30, 2026

Do you know why this action stopped working ? It used to work in the past.

However it was never very popular. I think with modern AI agents we can get build/find a better solution to triaging old issues, so I don't mind seeing this go.

I am curious why it stopped doing its job though.

@mcbarton
Copy link
Copy Markdown
Contributor Author

mcbarton commented Apr 30, 2026

Do you know why this action stopped working ? It used to work in the past.

However it was never very popular. I think with modern AI agents we can get build/find a better solution to triaging old issues, so I don't mind seeing this go.

I am curious why it stopped doing its job though.

I have no idea. I did try Googling about the stale.yml file, and although I could find a few repos including it, I couldn't find any documentation about it.

@sbc100
Copy link
Copy Markdown
Collaborator

sbc100 commented Apr 30, 2026

@mcbarton
Copy link
Copy Markdown
Contributor Author

The docs are here: https://github.com/marketplace/actions/close-stale-issues

That is the documentation for the action I use in the workflow file in this PRs description . Maybe in older versions it worked differently and didn't require the workflow file, and it had some breaking change at some point

@sbc100
Copy link
Copy Markdown
Collaborator

sbc100 commented Apr 30, 2026

Ah, yes, this is the original bot that we used: https://github.com/probot/stale

@sbc100 sbc100 merged commit d0797f1 into emscripten-core:main May 11, 2026
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants