[Intermediate]: Add user name to reminder bot

[exploreriii]

🧩 Intermediate Contributors

This issue is intended for contributors who already have some familiarity with the
Hiero Python SDK codebase and contribution workflow.

You should feel comfortable:

• navigating existing source code and examples
• understanding SDK concepts without step-by-step guidance
• following the standard PR workflow without additional onboarding

If this is your very first contribution to the project, we recommend starting with a few
Good First Issues before working on this one.

🐞 Problem Description

Reminder bot is a workflow that notifies posts on issues that have had no pull request created after 10 days of being assigned.

Currently it posts this message:
"
Hi, this is ReminderBot. This issue has been assigned but has had no pull request created. Are you still planning on working on the issue?

From the Python SDK Team
"

Right now if there are multiple users posting on a post, it can be confusing to know who it should apply to.
It will be clearer if we say to whom the issue was assigned, so they know to create a pull request.

💡 Expected Solution

Ensure that issue reminder bot extracts the assignee name.

before:
Hi, this is ReminderBot. This issue has been assigned but has had no pull request created. Are you still planning on working on the issue?

From the Python SDK Team

after:
Hi, [name] this is ReminderBot. You have been assigned but no pull request has been created. Are you still planning on working on the issue?

From the Python SDK Team

🧠 Implementation Notes

Edit
.github/scripts/issue_reminder_no_pr.sh

this section:
MESSAGE="Hi, this is ReminderBot. This issue has been assigned but has had no pull request created. Are you still planning on working on the issue?

You'll need to add in a variable for the user name.

This means extracting it from the github api

In the case there are multiple assignees, we can extract both (or all)

e.g.
Hi @alice @bob 👋

This issue has been assigned but no pull request has been created yet.
Are you still planning on working on it?

✅ Acceptance Criteria

To merge this issue, the pull request must:

• Fully address the problem described above
• Follow existing project conventions and patterns
• Include tests or example updates where appropriate
• Pass all CI checks
• Include a valid changelog entry
• Use DCO and GPG-signed commits

📚 Additional Context or Resources

• SDK Developer Docs
• SDK Developer Training

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

✅ Successfully generated implementation plan.

💡 Use @coderabbitai <feedback> to replan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• [Intermediate]: Refactor .github/scripts/gfi_notify_team.js #1212
• [Intermediate]: Create workflow that sends a reminder to link an isssue to a PR #1144
• [Good First Issue]: Rename pr_missing_linked_issue workflows #1197
• test reminderbot: no PR created #1071

🔗 Related PRs

#1123 - feat: Add workflow to notify team about Good first issues [merged]
#1137 - feat: create new .github/ISSUE_TEMPLATE/05_intermediate_issue.yml [merged]
#1150 - ci: reduce office-hours reminder spam by posting only on most recent PR per user [merged]
#1162 - chore: move helpful references to additional context [merged]
#1173 - feat(ci): add workflow to remind pull requests to link issues [merged]

👤 Suggested Assignees

• exploreriii
• prajeeta15
• kplnosmn94-droid
• AntonioCeppellini
• TianyangRen

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[coderabbitai]

Coding Plan

Approach

Modify the issue reminder bot to extract and mention assignee usernames in reminder comments, making it clear who is being reminded about creating a pull request for assigned issues.

Observations

This is a GitHub repository using GitHub Actions workflows to automate issue management. The reminder bot is implemented as a bash script (.github/scripts/issue_reminder_no_pr.sh) that runs daily via workflow (.github/workflows/bot-issue-reminder-no-pr.yml). The script uses gh api commands with jq for JSON filtering to fetch open assigned issues, checks for linked PRs, and posts reminder comments when issues have been assigned for 7+ days without PR activity. The codebase follows consistent patterns for GitHub API interaction, with bash scripts using REST API endpoints and inline jq filtering.

Assumptions

Assumption 1: Issue JSON Structure

Options Considered:

• Parse assignees from API response in each iteration
• Extract all assignees upfront before processing
• Use existing ALL_ISSUES_JSON within processing loop

Chosen Option: Use existing ALL_ISSUES_JSON within processing loop

Rationale: The plan explicitly states 'Parse the issue JSON (already available from ALL_ISSUES_JSON)' indicating the data is already available in the current processing context

Assumption 2: Multiple Assignees Format

Options Considered:

• Join usernames with spaces (e.g., '@alice @bob')
• Join usernames with commas (e.g., '@alice, @bob')
• Use separate lines for each mention

Chosen Option: Join usernames with spaces (e.g., '@alice @bob')

Rationale: The plan specifies 'Join multiple usernames with spaces to create the mention string (e.g., "@alice @bob")'

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Extract and Format Assignee Information

This phase modifies the core message generation logic to extract assignee usernames from issue data and format them as GitHub @mentions.

Task 1: Extract Assignee Usernames from Issue JSON

Extract the list of assignee usernames for each issue being processed.

• In .github/scripts/issue_reminder_no_pr.sh, within the issue processing loop where each issue is evaluated, add logic to extract assignees using jq
• Parse the issue JSON (already available from ALL_ISSUES_JSON) to get the .assignees[].login array for the current issue
• Use jq with the -r flag to output raw username strings
• Store the list of usernames in a variable for formatting

Task 2: Format Assignees as GitHub Mentions

Convert the extracted usernames into the @mention format expected by GitHub.

• Transform each username by prefixing with @ symbol
• Join multiple usernames with spaces to create the mention string (e.g., "@alice @bob")
• Handle the case of a single assignee vs multiple assignees (same format works for both)
• Store the formatted mention string in a variable like ASSIGNEE_MENTIONS

Task 3: Update Message Template with Assignee Mentions

Replace the generic greeting with personalized @mentions in the reminder message.

• Locate the MESSAGE variable definition in .github/scripts/issue_reminder_no_pr.sh
• Update the message format from "Hi, this is ReminderBot..." to match the suggested format in the ticket's implementation notes
• Include the ASSIGNEE_MENTIONS variable at the start: "Hi ${ASSIGNEE_MENTIONS} 👋"
• Adjust the message text to be more direct: "This issue has been assigned but no pull request has been created yet. Are you still planning on working on it?"
• Maintain the existing signature footer "From the Python SDK Team"
• Ensure proper line breaks using \n\n for paragraph separation

🤖 Prompt for AI agents

Modify the issue reminder bot to extract assignees and personalize reminder
messages with @mentions.

In `.github/scripts/issue_reminder_no_pr.sh`:
- Within the issue processing loop, extract assignee usernames from the issue
JSON using jq to parse `.assignees[].login` with the `-r` flag
- Format extracted usernames by prefixing each with `@` and joining with spaces
(e.g., "@alice @bob")
- Store the formatted mentions in a variable like `ASSIGNEE_MENTIONS`
- Update the `MESSAGE` variable to use the new format: "Hi ${ASSIGNEE_MENTIONS}
👋" followed by "This issue has been assigned but no pull request has been
created yet. Are you still planning on working on it?"
- Maintain the existing signature "From the Python SDK Team" with proper line
breaks using `\n\n`

---

🚀 Next Steps

🤖 All AI agent prompts combined

Modify the issue reminder bot to extract assignees and personalize reminder
messages with @mentions.

In `.github/scripts/issue_reminder_no_pr.sh`:
- Within the issue processing loop, extract assignee usernames from the issue
JSON using jq to parse `.assignees[].login` with the `-r` flag
- Format extracted usernames by prefixing each with `@` and joining with spaces
(e.g., "@alice @bob")
- Store the formatted mentions in a variable like `ASSIGNEE_MENTIONS`
- Update the `MESSAGE` variable to use the new format: "Hi ${ASSIGNEE_MENTIONS}
👋" followed by "This issue has been assigned but no pull request has been
created yet. Are you still planning on working on it?"
- Maintain the existing signature "From the Python SDK Team" with proper line
breaks using `\n\n`

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- @coderabbitai You can skip phase 3. Add a simple unit test case for phase 2.
- @coderabbitai For assumption 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!

[drtoxic69]

Hey @exploreriii
I am interested in this issue and would like to work on it.

[exploreriii]

Thank you!!!