chore(ci): add stale issue triage workflow by EliteCoder18 · Pull Request #497 · bitcoindevkit/bdk_wallet

EliteCoder18 · 2026-06-07T00:22:06Z

Description

Part of #410
Closes #386

Adds .github/workflows/stale.yml using actions/stale@v10 to automatically label and close inactive issues and abandoned PRs.

Issues inactive for 180 days → stale label → closed after 30 more days
PRs inactive for 180 days → stale label → closed after 30 more days
Exempt: labels release,security,audit,do-not-close,good first issue for issues and blocked,security,do-not-close for PR
Runs weekly on Mondays at 09:00 UTC
PR trigger forces dry-run mode automatically for safe CI validation

Notes to the reviewers

Recommend a workflow_dispatch dry run with debug_only=true right after merge to preview impact before the Monday cron fires
do-not-close and blocked exemption labels don't exist in the repo yet, create them before merging if you want manual override capability

Changelog notice

ci: Automated stale issue and PR triage workflow

Before submitting

I followed the contribution guidelines
This PR breaks the existing API

codecov · 2026-06-08T14:25:31Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.96%. Comparing base (d8e006f) to head (d466b08).
⚠️ Report is 6 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #497      +/-   ##
==========================================
+ Coverage   80.93%   80.96%   +0.02%     
==========================================
  Files          24       24              
  Lines        5482     5489       +7     
  Branches      247      247              
==========================================
+ Hits         4437     4444       +7     
  Misses        968      968              
  Partials       77       77

Flag	Coverage Δ
rust	`80.96% <ø> (+0.02%)`	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

notmandatory

Concept ACK.

We'll discuss with the team at our next call to confirm the time frames for making something stale make sense to everyone.

notmandatory · 2026-06-08T15:15:18Z

+          days-before-issue-close: 30
+          stale-issue-label: 'stale'
+          stale-issue-message: >
+            This issue has been inactive for 180 days and labeled **stale** Comment to keep it open. It will be closed in 30 days if there is no activity.


Suggested change

This issue has been inactive for 180 days and labeled **stale** Comment to keep it open. It will be closed in 30 days if there is no activity.

This issue has been inactive for 180 days and labeled **stale**, comment to keep it open. It will be closed in 30 days if there is no activity.

Updated in the latest rebase, thanks.

Dmenec

Concept ACK. Just a little nit on close reason.

Dmenec · 2026-06-10T15:59:56Z

+            This issue has been inactive for 180 days and labeled **stale** Comment to keep it open. It will be closed in 30 days if there is no activity.
+          close-issue-message: >
+            Closed after 210 days of inactivity. Feel free to reopen if this is still relevant.
+          close-issue-reason: completed


not_planned fits an inactivity close better (as mentioned in actions/stale#789), and since it's the default option we could just drop the line.

Good point, updated.

ValuedMammal

I would be generous and leave PRs open for 180 days. Suggest removing discussion from exempt labels. If there are long running discussions, they can happen in https://github.com/bitcoindevkit/bdk_wallet/discussions

EliteCoder18 · 2026-06-11T22:29:05Z

I would be generous and leave PRs open for 180 days. Suggest removing discussion from exempt labels. If there are long running discussions, they can happen in https://github.com/bitcoindevkit/bdk_wallet/discussions

@ValuedMammal Thanks, updated the exempt labels. I also adjusted the PR timeout to 180 days.

ValuedMammal · 2026-06-12T16:05:01Z

I would be generous and leave PRs open for 180 days. Suggest removing discussion from exempt labels. If there are long running discussions, they can happen in https://github.com/bitcoindevkit/bdk_wallet/discussions

@ValuedMammal Thanks, updated the exempt labels. I also adjusted the PR timeout to 180 days.

Can we update the {stale|close}-pr-message to reflect the 180/210 days of inactivity as well.

EliteCoder18 · 2026-06-16T20:50:47Z

Updated the workflow based on the Lib Standup discussion:

Pinned actions/stale to a commit hash for improved security.
Simplified the PR close message.
Fixed indentation and removed unnecessary blank lines.

notmandatory

ACK d466b08

Great first step in helping close old issues and PRs in this repo. If all goes well I'd like to see this workflow in other repos in the org.

oleonardolima

cACK

I left a few suggestions.

oleonardolima · 2026-06-18T01:51:44Z

+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@eb5cf3af3ac0a1aa4c9c45633dd1ae542a27a899 # v10


I didn't know that stale was an official action, it can have the version used directly instead of the hash.

Even though it's an official plugin I think Zizmor action will still complain so I don't see a problem leaving the hash since it returns the same version and is marginally safer.

oleonardolima · 2026-06-18T01:52:41Z

+            Closed after 210 days of inactivity. Feel free to reopen if this is still relevant.
+          exempt-pr-labels: 'blocked,security,do-not-close'
+          exempt-all-pr-milestones: true
+          exempt-draft-pr: true


I don't think draft PRs should be exempt.

It's true they still clutter up the active PRs list so I agree they don't need to be exempted.

oleonardolima · 2026-06-18T01:53:03Z

+      debug_only:
+        description: 'Dry-run mode (no writes)'
+        required: false
+        default: 'false'
+        type: choice
+        options:
+          - 'false'
+          - 'true'


question: are these required ?

AFAIK this isn't required but more of a "nice to have" while we're rolling this out. Could be removed once this workflow is enabled and we're comfortable with all the settings.

oleonardolima · 2026-06-18T01:54:06Z

+        with:
+          days-before-issue-stale: 180
+          days-before-issue-close: 30
+          stale-issue-label: 'stale'
+          stale-issue-message: >
+            This issue has been inactive for 180 days and labeled **stale**, comment to keep it open. It will be closed in 30 days if there is no activity.
+          close-issue-message: >
+            Closed after 210 days of inactivity. Feel free to reopen if this is still relevant.
+          exempt-issue-labels: 'release,security,audit,do-not-close,good first issue'
+          exempt-all-issue-milestones: true
+          days-before-pr-stale: 180
+          days-before-pr-close: 30
+          stale-pr-label: 'stale'
+          stale-pr-message: >
+            This pull request has had no activity for 180 days and has been labeled **stale**. If this work is still in progress or waiting on review, a comment or push will remove the label. PRs with no further activity for 30 days will be closed.
+          close-pr-message: >
+            Closed after 210 days of inactivity. Feel free to reopen if this is still relevant.
+          exempt-pr-labels: 'blocked,security,do-not-close'
+          exempt-all-pr-milestones: true
+          exempt-draft-pr: true
+          remove-stale-when-updated: true
+          ascending: true
+          operations-per-run: 600
+          debug-only: ${{ github.event_name == 'pull_request' || github.event.inputs.debug_only == 'true' }}
+          enable-statistics: true


I think it'd help with readability and updating it in the future by splitting into different jobs (if possible): issues, prs, ...

github-project-automation Bot added this to BDK Wallet Jun 7, 2026

ValuedMammal assigned EliteCoder18 Jun 7, 2026

ValuedMammal added the github_actions Pull requests that update GitHub Actions code label Jun 7, 2026

ValuedMammal added this to the Wallet 4.0.0 milestone Jun 7, 2026

notmandatory moved this to In Progress in BDK Wallet Jun 8, 2026

notmandatory reviewed Jun 8, 2026

View reviewed changes

EliteCoder18 marked this pull request as ready for review June 8, 2026 15:23

EliteCoder18 requested review from ValuedMammal and oleonardolima as code owners June 8, 2026 15:23

Dmenec reviewed Jun 10, 2026

View reviewed changes

ValuedMammal reviewed Jun 10, 2026

View reviewed changes

EliteCoder18 force-pushed the feat/issue-triage-automation branch from 0e0f788 to bb1fc1f Compare June 11, 2026 22:21

EliteCoder18 closed this Jun 11, 2026

github-project-automation Bot moved this from In Progress to Done in BDK Wallet Jun 11, 2026

EliteCoder18 reopened this Jun 11, 2026

EliteCoder18 force-pushed the feat/issue-triage-automation branch from bb1fc1f to 3f18adc Compare June 12, 2026 18:25

chore(ci): add stale issue and pr automation

d466b08

EliteCoder18 force-pushed the feat/issue-triage-automation branch from 3f18adc to d466b08 Compare June 16, 2026 20:31

notmandatory moved this from Done to In Progress in BDK Wallet Jun 16, 2026

notmandatory removed the status in BDK Wallet Jun 16, 2026

notmandatory moved this to Needs Review in BDK Wallet Jun 16, 2026

notmandatory approved these changes Jun 16, 2026

View reviewed changes

oleonardolima reviewed Jun 18, 2026

View reviewed changes

	This issue has been inactive for 180 days and labeled stale Comment to keep it open. It will be closed in 30 days if there is no activity.
	This issue has been inactive for 180 days and labeled stale, comment to keep it open. It will be closed in 30 days if there is no activity.

Conversation

EliteCoder18 commented Jun 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Notes to the reviewers

Changelog notice

Before submitting

Uh oh!

codecov Bot commented Jun 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

notmandatory left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Dmenec left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ValuedMammal left a comment

Choose a reason for hiding this comment

Uh oh!

EliteCoder18 commented Jun 11, 2026

Uh oh!

ValuedMammal commented Jun 12, 2026

Uh oh!

EliteCoder18 commented Jun 16, 2026

Uh oh!

notmandatory left a comment

Choose a reason for hiding this comment

Uh oh!

oleonardolima left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

oleonardolima Jun 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

EliteCoder18 commented Jun 7, 2026 •

edited

Loading

codecov Bot commented Jun 8, 2026 •

edited

Loading

notmandatory left a comment •

edited

Loading

oleonardolima Jun 18, 2026 •

edited

Loading