chore: Edit .github/scripts/bot-assignment-check.sh so max assignment limit only applies to issues, it excludes PRs

[AkshayKumarSahu]

Description:

Related issue(s):

Fixes #1717

Notes for reviewer:

Checklist

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

[coderabbitai]

Warning

Rate limit exceeded

@AkshayKumarSahu has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 5 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[Copilot]

Pull request overview

Updates the assignment-limit guard script so the “max concurrent assignments” rule counts only issues, not pull requests—matching the intended workflow behavior from #1717.

Changes:

• Adjust assignments_count() in the assignment-check bot script to exclude PRs from the open-assignment count.
• Update bot limit-exceeded messages to clarify they apply to issue assignments.
• Add a changelog entry describing the behavior change.

Reviewed changes

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

File	Description
CHANGELOG.md	Documents the change that assignment limits now count only issues, not PRs.
.github/scripts/bot-assignment-check.sh	Updates assignment counting logic and refines user-facing messaging around issue-only limits.

Comments suppressed due to low confidence (1)

.github/scripts/bot-assignment-check.sh:83

• This message now says “1 open issue assignment”, but later in the same heredoc the restrictions list still says “Maximum 1 open assignment at a time”. Update the wording throughout this message to consistently refer to “issue assignments” (since PRs are no longer counted) to avoid confusing users.

Your account currently has limited assignment privileges with a maximum of **1 open issue assignment** at a time.

You currently have $count open issue(s) assigned.  Please complete and merge your existing assignment before requesting a new one.

**Current Restrictions:**

---

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

[tech0priyanshu]

hii @AkshayKumarSahu i would like to see test evidence

[exploreriii]

@tech0priyanshu could you specify pleae what that would involve, else could you test it please :)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

@@           Coverage Diff           @@
##             main    #1739   +/-   ##
=======================================
  Coverage   93.25%   93.25%           
=======================================
  Files         141      141           
  Lines        9061     9061           
=======================================
  Hits         8450     8450           
  Misses        611      611           

🚀 New features to boost your workflow:

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

[AkshayKumarSahu]

@tech0priyanshu

Attached SS of 3 diff profile which have issues assigned

[exploreriii]

Request step security assistance @hiero-ledger/security-maintainers please

[tech0priyanshu]

@AkshayKumarSahu fine lGTM

cc @exploreriii

[github-actions]

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:

• Resolving Merge Conflicts
• Rebasing Guide

Thank you for contributing!