[Beginner]: Ensure no duplicate linkbot posts

[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

Linkbot is currently posting over and over on an issue that does not have a linked issue to their PR.

.github/scripts/bot-pr-missing-linked-issue.js <--- logic
.github/workflows/bot-pr-missing-linked-issue.yml <-- trigger

We should ensure it never posts duplicate posts

💡 Proposed Solution

Ensure it never posts duplicate posts in an issue

For example, avoid this:
#1462

👩‍💻 Implementation Steps

To do that, add a new variable called LINKBOT_MARKER and make it hidden html so it doesn't render to the user

Pass that linkbot marker in the comment.

Check for the presence of the linkbot marker before deciding whether to post a new comment.
if there is a linkbot marker in the issue thread, its already posted, so can skip posting again.

We have several examples of this technique in e.g.
.github/scripts/bot-mentor-assignment.js

✅ Acceptance Criteria

To be able to merge a pull request for this issue, we need:

• Assignment: You must be assigned to the issue, comment: /assign in the issue to get assigned see guide
• Changelog Entry: Correct changelog entry see guide
• Signed commits: commits must be DCO and GPG key signed see guide
• All Tests Pass: our workflow checks like unit and integration tests must pass
• Issue is Solved: The implementation fully addresses the issue requirements as described above
• No Further Changes are Made: Code review feedback has been addressed and no further changes are requested

📋 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 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.

🤔 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 from GitHub
gh issue view 1463 --repo hiero-ledger/hiero-sdk-python --json title,body,labels,author,createdAt,comments

Length of output: 6778

---

🏁 Script executed:

#!/bin/bash
# Read the current bot script that needs modification
cat .github/scripts/bot-pr-missing-linked-issue.js

echo "==================== SEPARATOR ===================="

# Read the reference script to see marker pattern
cat .github/scripts/bot-mentor-assignment.js

echo "==================== SEPARATOR ===================="

# Read the workflow file
cat .github/workflows/bot-pr-missing-linked-issue.yml

Length of output: 12152

---

@github-actions[bot], I'll create a plan to fix the duplicate linkbot posts issue.

Task: Prevent Duplicate LinkBot Comments

The issue is that LinkBot currently checks for duplicate comments by searching for the text "this is LinkBot" which is not robust. We need to implement a hidden HTML marker pattern (similar to the mentor assignment bot) to reliably detect if LinkBot has already commented.

Changes needed:

1. Add a hidden HTML marker constant to the bot script
2. Include the marker in the comment body
3. Update the duplicate detection logic to check for the marker

';

2. **Update the duplicate check logic** (around line 48) to check for the marker instead of text:
```diff
-    const alreadyCommented = comments.data.some(comment =>
-      comment.body.includes("this is LinkBot")
-    );
+    const alreadyCommented = comments.data.some(comment =>
+      comment.body?.includes(LINKBOT_MARKER)
+    );

3. Include the marker in the comment body (around line 57) at the beginning:

-      const commentBody = [
+      const commentBody = `${LINKBOT_MARKER}
+` + [
         `Hi @${prData.user.login}, this is **LinkBot** 👋`,

Complete modified section should look like:

module.exports = async ({ github, context }) => {
  const LINKBOT_MARKER = '<!-- LinkBot Missing Issue -->';
  
  let prNumber;
  try {
    // ... existing code ...

    const comments = await github.rest.issues.listComments({
      owner: context.repo.owner,
      repo: context.repo.repo,
      issue_number: prNumber,
    });

    const alreadyCommented = comments.data.some(comment =>
      comment.body?.includes(LINKBOT_MARKER)
    );

    if (alreadyCommented) {
      console.log('LinkBot already commented on this PR');
      return;
    }

    if (!regex.test(body)) {
      const commentBody = `${LINKBOT_MARKER}
` + [
        `Hi @${prData.user.login}, this is **LinkBot** 👋`,
        ``,
        `Linking pull requests to issues helps us significantly with reviewing pull requests and keeping the repository healthy.`,
        ``,
        `🚨 **This pull request does not have an issue linked.**`,
        ``,
        `Please link an issue using the following format:`,
        `- Fixes #123`,
        ``,
        `📖 Guide:`,
        `[docs/sdk_developers/training/workflow/how_to_link_issues.md](https://github.com/${context.repo.owner}/${context.repo.repo}/blob/main/docs/sdk_developers/training/workflow/how_to_link_issues.md)`,
        ``,
        `If no issue exists yet, please create one:`,
        `[docs/sdk_developers/creating_issues.md](https://github.com/${context.repo.owner}/${context.repo.repo}/blob/main/docs/sdk_developers/creating_issues.md)`,
        ``,
        `Thanks!`
      ].join('\n');

      // ... rest of existing code ...
    }
  } catch (error) {
    // ... existing error handling ...
  }
};

Why this works:

• The HTML comment <!-- LinkBot Missing Issue --> is invisible to users but present in the comment body
• It provides a reliable, unchanging marker to detect if LinkBot has already commented
• This follows the same pattern used successfully in bot-mentor-assignment.js
• The optional chaining ?.includes() safely handles null/undefined comment bodies
  -->

---

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

[parvninama]

Hii , I’d be happy to take this on next. I’m currently finishing up PR #1443 and can start this in parallel if that works.

[github-actions]

👋 Hi @parvninama! If you'd like to work on this issue, please comment /assign to get assigned.

[parvninama]

/assign