[Beginner]: Update max assignments reached rejection message with more information

[exploreriii]

🐥 Beginner Friendly

This issue is intended for contributors who have previously completed a Good First Issue in Hiero and are at a beginner level.
We recognize that gaining confidence and building skills are equally important steps in the open-source contributor journey.
The purpose of this issue—and others listed under Find a beginner issue—is to provide a supportive, low-pressure environment where you can learn, practice, and grow your contribution skills with confidence.

👾 Description of the issue

Whe users try to get assigned to good first issues or beginner issues, and have reached their max assignments, they cannot be assigned.

For example:
#1723

However, from a users perspective, the comment does not tell them which issues they are assigned to and they need to figure that out - which can be difficult when there are many issues in a repository.

💡 Proposed Solution

Improve the comment that tells them they have two open assignments, to additionally tell them which PRs they are assigned to, so they can clear those first.E

👩‍💻 Implementation Steps

Edit
.github/scripts/bot-beginner-assign-on-comment.js
and
.github/scripts/bot-gfi-assign-on-comment.js

expand:

                : `Hi @${requesterUsername}, you already have **2 open assignments**. Please finish one before requesting another.`;

and

        const message = `👋 Hi @${commenter}, you already have **2 open assignments**. Please finish one before requesting another.`;

ensure this comment includes details on what thy are assigned to.

To do that you'll need to update these functions:

async function getOpenAssignments(username) {

to return issue information like the PR number etc

  return issues
    .filter(issue => !issue.pull_request)
    .map(issue => ({
      number: issue.number,
      title: issue.title,
      url: issue.html_url,
    }));
}

and inject the result eg

  const message = `👋 Hi @${commenter}, you already have **${openCount} open assignment${openCount > 1 ? 's' : ''}**:

${assignmentList}

✅ Acceptance Criteria

• The issue is solved:
  My changes do exactly what the issue asked for.

• I did not add extra changes:
  I did not modify anything that was not mentioned in the issue description.

• Nothing else was broken:
  All existing features still work the same as before.

• All checks pass:
  The automated tests (unit and integration tests) run successfully.

📋 Step-by-Step Contribution Guide

• Assignment: You must be assigned to the issue, comment: /assign in the issue to get assigned see guide
• Fork, Branch and Work on the issue: Create a copy of the repository, create a branch for the issue and solve the problem. For instructions, please read our Contributing guide file. Further help can be found at Set-up Training (including the Windows Setup Guide for Windows users) and Workflow Training.
• DCO and GPG key sign each commit : each commit must be -s and -S signed. An explanation on how to do this is at Signing Guide
• Add a Changelog Entry : your pull request will require a changelog. Read Changelog Entry Guide to learn how.
• Push and Create a Pull Request : Once your issue is resolved, and your commits are signed, and you have a changelog entry, push your changes and create a pull request. Detailed instructions can be found at Submit PR Training, part of Workflow Training.
• You did it 🎉: A maintainer or committer will review your pull request and provide feedback. If approved, we will merge the fix in the main branch. Thanks for being part of the Hiero community as an open-source contributor ❤️

IMPORTANT You will ONLY be assigned to the issue if you comment: /assign
IMPORTANT Your pull request CANNOT BE MERGED until you add a changelog entry AND sign your commits each with git commit -S -s -m "chore: your commit message" with a GPG key setup.

🤖 AI Usage Guidelines

You are welcome to use AI to help you understand and solve this issue.

Because AI tools can sometimes make mistakes, please take care to:

• Only implement what is described in this issue
• Avoid changing anything else in the file
• Be careful when modifying parameters or return statements, as this may affect runtime behavior

If you're unsure, ask your mentor or the maintainers for help — they can provide expert Python SDK guidance and point you to the right examples or methods.

🤔 Additional Information

For more help, we have extensive documentation:

• SDK Developer Docs
• SDK Developer Training

Additionally, we invite you to join our community on our Discord server.

We also invite you to attend each Wednesday, 2pm UTC our Python SDK Office Hour and Community Calls. The Python SDK Office hour is for hands-on-help and the Community Call for general community discussion.

You can also ask for help in a comment below!

[github-actions]

@coderabbitai plan

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Fetch the issue details
gh issue view 1724 --repo hiero-ledger/hiero-sdk-python --json title,body,labels,assignees,author,createdAt,updatedAt,comments

Length of output: 7606

---

🏁 Script executed:

#!/bin/bash
# Read the two JavaScript files that need to be modified
echo "=== bot-beginner-assign-on-comment.js ==="
cat .github/scripts/bot-beginner-assign-on-comment.js

echo -e "\n\n=== bot-gfi-assign-on-comment.js ==="
cat .github/scripts/bot-gfi-assign-on-comment.js

Length of output: 27062

---

@github-actions[bot], I'll create a plan to enhance the max assignments rejection message with detailed information about current assignments.

Task: Enhance max assignments rejection message with assignment details

The plan involves modifying two GitHub Actions bot scripts to provide users with specific information about their current open assignments when they reach the maximum limit.

Changes needed:

1. Update getOpenAssignments() functions to return issue details (number, title, URL) instead of just a count
2. Modify rejection messages to display a formatted list of current assignments
3. Ensure both spam users (1 max) and regular users (2 max) see helpful information

---

💡 Use @coderabbitai plan to create a plan for code changes

[om12prakash]

/assign

[github-actions]

Hi @om12prakash 👋

This issue has been assigned but no pull request has been created yet.
Are you still planning on working on it?
If you are, please create a draft PR linked to this issue or comment /working to let us know.
If you’re no longer able to work on this issue, you can comment /unassign to release it.

From the Python SDK Team

[om12prakash]

/working