Skip to content

chore: Update .github/scripts/bot-inactivity-unassign.sh to skip if 'discussion' label is added#1771

Draft
AkshayKumarSahu wants to merge 18 commits intohiero-ledger:mainfrom
AkshayKumarSahu:1583_1
Draft

chore: Update .github/scripts/bot-inactivity-unassign.sh to skip if 'discussion' label is added#1771
AkshayKumarSahu wants to merge 18 commits intohiero-ledger:mainfrom
AkshayKumarSahu:1583_1

Conversation

@AkshayKumarSahu
Copy link
Contributor

Description:

Related issue(s):

Fixes #1583

Notes for reviewer:

Checklist

  • Documented (Code comments, README, etc.)
  • Tested (unit, integration, etc.)

Signed-off-by: AkshayKumarSahu <akshaykumar15031999@gmail.com>
@AkshayKumarSahu AkshayKumarSahu requested a review from a team as a code owner February 9, 2026 19:32
Copilot AI review requested due to automatic review settings February 9, 2026 19:32
@AkshayKumarSahu AkshayKumarSahu requested a review from a team as a code owner February 9, 2026 19:32
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the GitHub automation that unassigns users / closes stale PRs to not take action when a linked PR is intentionally parked for discussion via a discussion label (Fixes #1583).

Changes:

  • Add a discussion label check in the inactivity bot script to skip closing/unassigning when present.
  • Add a corresponding entry to CHANGELOG.md.

Reviewed changes

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

File Description
.github/scripts/bot-inactivity-unassign.sh Adds logic to detect the discussion label on linked PRs and skip inactivity actions.
CHANGELOG.md Documents the new inactivity-bot behavior.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 9, 2026

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Adds a check to the inactivity bot script to skip closing/unassigning PRs labeled "discussion" and logs skipped PRs; also updates CHANGELOG.md to record the new behavior.

Changes

Cohort / File(s) Summary
Inactivity Bot Script
.github/scripts/bot-inactivity-unassign.sh
Fetches PR labels, detects a discussion label, logs a skip message like [SKIP] PR #<num> has 'discussion' label — skipping close & unassign, and continues to avoid closing or unassigning those PRs.
Changelog
CHANGELOG.md
Adds an Unreleased entry documenting the inactivity bot now skips PRs with the discussion label.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 6
✅ Passed checks (6 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: updating bot-inactivity-unassign.sh to skip PRs with 'discussion' label.
Description check ✅ Passed The description references the linked issue #1583 and briefly explains the purpose of the PR, which is related to the changeset.
Linked Issues check ✅ Passed The code changes implement all primary requirements from issue #1583: adding a check for 'discussion' label, skipping PRs with that label, and updating the CHANGELOG [#1583].
Out of Scope Changes check ✅ Passed All changes are scoped to the requirements in issue #1583: modifications to bot-inactivity-unassign.sh and CHANGELOG.md only, with no unrelated changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

No actionable comments were generated in the recent review. 🎉


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

Copy link
Contributor

@exploreriii exploreriii left a comment

Choose a reason for hiding this comment

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

Hi @AkshayKumarSahu
There are quite a lot of changes here

Testing this would be difficult, but is worthwhile and a good next challenge

Could you:

  • merge this PR to your forks main
  • change inactivity to just 10 minutes, for example
  • go to settings
  • enable issues
  • go to issues, create a label 'discussion'

try and trigger this bot, eg

  • create pull request
  • be inactive for 10 minutes, expect to unassign
  • create a pull request with 'discussion'
  • be inactive for 10 minutes, expect not to unassign
    docs/sdk_developers/training/testing_forks.md

@exploreriii exploreriii marked this pull request as draft February 10, 2026 11:54
@exploreriii exploreriii added the status: needs developer revision PR has requested changes that the developer needs to implement label Feb 10, 2026
@github-actions
Copy link

Hi, this is MergeConflictBot.
Your pull request cannot be merged because it contains merge conflicts.

Please resolve these conflicts locally and push the changes.

Quick Fix for CHANGELOG.md Conflicts

If your conflict is only in CHANGELOG.md, you can resolve it easily using the GitHub web editor:

  1. Click on the "Resolve conflicts" button in the PR
  2. Accept both changes (keep both changelog entries)
  3. Click "Mark as resolved"
  4. Commit the merge

For all other merge conflicts, please read:

Thank you for contributing!

Signed-off-by: Akshay Kumar <akshaykumar15031999@gmail.com>
@github-actions
Copy link

Hello, this is the OfficeHourBot.

This is a reminder that the Hiero Python SDK Office Hours are scheduled in approximately 4 hours (14:00 UTC).

This session provides an opportunity to ask questions regarding this Pull Request.

Details:

Disclaimer: This is an automated reminder. Please verify the schedule here for any changes.

From,
The Python SDK Team

@exploreriii
Copy link
Contributor

@AkshayKumarSahu I noticed you have still got this PR to rest and merge, which is essential to be able to complete the next workflow you want to be assigned.

I will unassign you from #1721 while you complete this workflow
Thank you for your understanding

Signed-off-by: Akshay Kumar <akshaykumar15031999@gmail.com>
@AkshayKumarSahu
Copy link
Contributor Author

@AkshayKumarSahu I noticed you have still got this PR to rest and merge, which is essential to be able to complete the next workflow you want to be assigned.

I will unassign you from #1721 while you complete this workflow Thank you for your understanding

Sure go ahead, meanwhile i am testing the changes

@AkshayKumarSahu AkshayKumarSahu marked this pull request as ready for review February 14, 2026 17:44
@exploreriii
Copy link
Contributor

HI @AkshayKumarSahu were you abel to test this, adn do you have screenshots or links to show?

@exploreriii exploreriii added status: needs triage review PR needs a review from the triage team status: needs committer review PR needs a review from the committer team status: needs developer testing and removed status: needs developer revision PR has requested changes that the developer needs to implement labels Feb 15, 2026
@AkshayKumarSahu
Copy link
Contributor Author

HI @AkshayKumarSahu were you abel to test this, adn do you have screenshots or links to show?

gonna work on this today

@exploreriii exploreriii removed status: needs triage review PR needs a review from the triage team status: needs committer review PR needs a review from the committer team labels Feb 18, 2026
@tech0priyanshu
Copy link
Contributor

Hii @AkshayKumarSahu Thanks for contribution and efforts. Please have a look on comment posted by coderabbitai[bot] Copilot code review

@tech0priyanshu tech0priyanshu added the status: needs developer revision PR has requested changes that the developer needs to implement label Feb 18, 2026
@exploreriii
Copy link
Contributor

Hi @AkshayKumarSahu do you need any help with the testing please?

@exploreriii exploreriii removed the status: needs developer revision PR has requested changes that the developer needs to implement label Feb 21, 2026
@Akshat8510 Akshat8510 marked this pull request as draft February 21, 2026 06:31
…n.sh

- Add TEST_DOCUMENTATION.md: Complete test documentation with all test cases
- Add TEST_EXECUTION_DETAILED.md: Detailed execution report with inputs/outputs
- Add TEST_QUICK_REFERENCE.md: Quick reference guide for running tests
- Add test-execution-log.txt: Raw test execution output (11/11 tests passed)

Tests validate the discussion label protection feature that prevents
auto-closing PRs labeled with 'discussion' regardless of inactivity.
- Comprehensive test suite with 8 test cases (11 assertions)
- Mock system for GitHub CLI commands
- Tests discussion label protection feature
- All tests passing (11/11)
- Includes setup, execution, validation, and cleanup
Signed-off-by: Akshay Kumar <akshaykumar15031999@gmail.com>
Signed-off-by: Akshay Kumar <akshaykumar15031999@gmail.com>
Signed-off-by: Akshay Kumar <akshaykumar15031999@gmail.com>
@exploreriii
Copy link
Contributor

Hi @AkshayKumarSahu have you read on how to test this on your fork please? docs/sdk_developers/training/testing_forks.md

Copy link
Contributor

@exploreriii exploreriii left a comment

Choose a reason for hiding this comment

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

Hi @AkshayKumarSahu would you please update us on the status of this PR?
I see some recent commits and want to check if it is tested on your fork and if you are ready for a review.
Also - i see some of your commits lost their signing DCO status, please check
Thanks

@exploreriii exploreriii added the status: needs developer revision PR has requested changes that the developer needs to implement label Mar 1, 2026
Copy link
Contributor

@exploreriii exploreriii left a comment

Choose a reason for hiding this comment

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

Hi @AkshayKumarSahu
Thanks for creating this and having a good go at the tests
This should be good to go

However, your DCO is not passing
can you check please these two commits are not signed correctly?
https://github.com/hiero-ledger/hiero-sdk-python/pull/1771/checks?check_run_id=65311182170

you can do
i = number of commits you want to soft revert
git reset --soft HEAD~i
then recommit and force push

@exploreriii
Copy link
Contributor

Hi @AkshayKumarSahu as a reminder please rebase, correct the signing, and move your changelog entry to the new unreleased version 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: needs developer revision PR has requested changes that the developer needs to implement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Beginner]: Update .github/scripts/bot-inactivity-unassign.sh to skip if 'discussion' label is added

4 participants