feat(workflow): Backlog management bot #11518

SamuelFialka · 2025-06-25T11:32:42Z

Description of Change

This PR introduces a GitHub Action workflow that helps manage stale issues in the repository.
The bot runs daily and performs the following tasks:

Skips pull requests and issues labeled as to-be-discussed
Automatically closes issues labeled awaiting-response or those without assignees after 90+ days of inactivity
Sends a reminder comment on assigned issues that have been inactive for over 90 days (without re-sending it more than once a week)
Avoids duplicate comments and respects special labels

The purpose of this automation is to keep the issue backlog clean, manageable, and up-to-date.
Feel free to suggest adjustments to label logic, thresholds, or wording in comments.

Tests scenarios

The script and workflow were successfully tested on GitHub Issues in my own fork. Behavior such as issue closure and reminder comments worked as expected.

Related links

Please provide links to related issue, PRs etc.

(eg. Closes #number of issue)

CLAassistant · 2025-06-25T11:32:49Z

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Samuel Fialka seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

github-actions · 2025-06-25T11:33:18Z

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello SamuelFialka, we appreciate your contribution to this project!

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 8a17a91

Copilot

Pull Request Overview

This PR adds an automated GitHub Action workflow and supporting script to manage stale issues by closing or reminding based on labels and inactivity thresholds.

Introduces a daily-scheduled workflow (backlog-bot.yml) that checks open issues and invokes the cleanup script.
Implements backlog-cleanup.js to fetch issues, skip exempt ones, close or comment on stale issues, and avoid duplicate reminders.
Tracks and logs totals for closed issues, sent reminders, and skipped items.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/backlog-bot.yml	New workflow to schedule and run the backlog cleanup.
.github/scripts/backlog-cleanup.js	Script implementing issue fetching, closing, and reminders.

Copilot · 2025-06-25T12:29:33Z

.github/scripts/backlog-cleanup.js

+        if (recentFriendlyReminder) {
+            totalSkipped++;
+            continue;
+        }
+
+        if (issue.labels.some(label => exemptLabels.includes(label.name))) {
+            totalSkipped++;
+            continue;
+        }
+


The early check for recentFriendlyReminder at line 92 prevents the automatic closure path from running when a reminder was recently posted. To ensure stale issues labeled for closure still get closed, move this check inside the reminder-sending branch so that only reminder logic is gated by recent comments.

Suggested change

if (recentFriendlyReminder) {

totalSkipped++;

continue;

}

if (issue.labels.some(label => exemptLabels.includes(label.name))) {

totalSkipped++;

continue;

}

if (issue.labels.some(label => exemptLabels.includes(label.name))) {

totalSkipped++;

continue;

}

if (shouldSendReminder(issue, exemptLabels, closeLabels)) {

if (!recentFriendlyReminder) {

await github.rest.issues.createComment({

owner,

repo,

issue_number: issue.number,

body: '⏰ Friendly Reminder: This issue has been inactive for a while. Please update or it may be closed.',

});

totalReminders++;

}

}

The originally proposed solution would ensure a early exit + it increments totalSkipped used for final summary at logs.

@lucasssvaz wdyt?

Copilot · 2025-06-25T12:29:34Z

.github/scripts/backlog-cleanup.js

+        const { data: comments } = await github.rest.issues.listComments({
+            owner,
+            repo,
+            issue_number: issue.number,
+            per_page: 10,
+        });


Limiting comment retrieval to 10 may miss recent reminders if an issue has many comments. Consider increasing per_page to 100 or implementing pagination so all comments within the last 7 days are checked.

Suggested change

const { data: comments } = await github.rest.issues.listComments({

owner,

repo,

issue_number: issue.number,

per_page: 10,

});

let comments = [];

let page = 1;

let fetchedComments;

do {

const { data } = await github.rest.issues.listComments({

owner,

repo,

issue_number: issue.number,

per_page: 100,

page,

});

fetchedComments = data;

comments = comments.concat(fetchedComments);

page++;

} while (fetchedComments.length === 100);

If there would be more than 10 comments, it is a sign that the issue is being worked on. In that case, the issue will be skipped because the 90 days of inactivity condition will not be met.

@lucasssvaz wdyt?

Will review this PR in a few days. For now testing the new BLE related stuff before 3.3.0 RC1. Will review ASAP.

Samuel Fialka added 2 commits June 20, 2025 10:13

feat(ci): add backlog management bot

4768f84

feat(ci): split script and action to separate files

8a17a91

SamuelFialka requested a review from lucasssvaz as a code owner June 25, 2025 11:32

lucasssvaz requested a review from Copilot June 25, 2025 12:28

Copilot AI reviewed Jun 25, 2025

View reviewed changes

lucasssvaz added the Type: CI & Testing label Jun 25, 2025

P-R-O-C-H-Y added the Status: Review needed Issue or PR is awaiting review label Jun 27, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(workflow): Backlog management bot #11518

feat(workflow): Backlog management bot #11518

Uh oh!

SamuelFialka commented Jun 25, 2025 •

edited

Loading

Uh oh!

CLAassistant commented Jun 25, 2025

Uh oh!

github-actions bot commented Jun 25, 2025 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Jun 25, 2025

Uh oh!

SamuelFialka Jun 25, 2025

Uh oh!

SamuelFialka Jun 25, 2025

Uh oh!

Copilot AI Jun 25, 2025

Uh oh!

SamuelFialka Jun 25, 2025

Uh oh!

SamuelFialka Jun 25, 2025

Uh oh!

lucasssvaz Jun 25, 2025

Uh oh!

Uh oh!

-        const { data: comments } = await github.rest.issues.listComments({
-            owner,
-            repo,
-            issue_number: issue.number,
-            per_page: 10,
-        });
+        let comments = [];
+        let page = 1;
+        let fetchedComments;
+        do {
+            const { data } = await github.rest.issues.listComments({
+                owner,
+                repo,
+                issue_number: issue.number,
+                per_page: 100,
+                page,
+            });
+            fetchedComments = data;
+            comments = comments.concat(fetchedComments);
+            page++;
+        } while (fetchedComments.length === 100);

feat(workflow): Backlog management bot #11518

Are you sure you want to change the base?

feat(workflow): Backlog management bot #11518

Uh oh!

Conversation

SamuelFialka commented Jun 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description of Change

Tests scenarios

Related links

Uh oh!

CLAassistant commented Jun 25, 2025

Uh oh!

github-actions bot commented Jun 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Copilot AI Jun 25, 2025

Choose a reason for hiding this comment

Uh oh!

SamuelFialka Jun 25, 2025

Choose a reason for hiding this comment

Uh oh!

SamuelFialka Jun 25, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jun 25, 2025

Choose a reason for hiding this comment

Uh oh!

SamuelFialka Jun 25, 2025

Choose a reason for hiding this comment

Uh oh!

SamuelFialka Jun 25, 2025

Choose a reason for hiding this comment

Uh oh!

lucasssvaz Jun 25, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

SamuelFialka commented Jun 25, 2025 •

edited

Loading

github-actions bot commented Jun 25, 2025 •

edited

Loading