[Intermediate]: Create a workflow if a PR is in draft, and commits are pushed, it prompts them ready to review?

[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

Sometimes pull requests get transformed to 'draft' status by a reviewer, if changes are requested.

There is a 'ready to review' button but we find sometimes users apply the changes but do not tell us it is ready for review again.

Therefore, we can create a workflow to remind users to request ready to review.

💡 Expected Solution

Add a workflow that triggers for draft PRs that have changes requested

When the developer pushes a change after the changes requested, it can remind them if it is ready to review.
It should only post a maximum of once.

🧠 Implementation Notes

When a PR is in draft and requested changes:

• listen for any on push changes

post a comment eg
Hi X, we noticed your pull request has had recent changes. Is your pull request ready to review again?
Please comment /review if so or click 'Ready to Review' button at the bottom right of the pull request.

Please make sure to craete a .github/workflow and its logic in .github/script, written in javascript ideally

✅ 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
• be a DCO and GPG key signed as git commit -S -s -m "chore: my change" with a GPG key set up

📚 Additional Context or Resources

• SDK Developer Docs
• SDK Developer Training

[github-actions]

@coderabbitai plan

[coderabbitai]

Coding Plan

Approach

Create a GitHub Actions workflow that reminds PR authors to mark their draft PRs as "ready for review" when they push new commits after receiving "changes requested" reviews. The bot should post a comment only once to avoid notification spam.

Observations

The repository has a mature GitHub Actions automation system with 30+ workflows following consistent patterns. Bot workflows use pull_request_target for fork safety, externalize logic to .github/scripts/*.js files, implement duplicate comment prevention via HTML markers, and include security hardening with step-security/harden-runner. All bots support a dry_run mode for testing. Existing similar bots like bot-merge-conflict.yml and bot-pr-missing-linked-issue.yml provide reference implementations for PR-triggered comment workflows.

Assumptions

Assumption 1: How to detect "changes requested" review state on synchronize events?

Options Considered:

1. Use GraphQL PullRequest.reviewDecision field which returns CHANGES_REQUESTED, APPROVED, or REVIEW_REQUIRED
2. Use REST API to list all reviews, filter to latest per reviewer, and check for CHANGES_REQUESTED state

Chosen Option: 1

Rationale: GraphQL reviewDecision provides the aggregate decision directly without manual deduplication logic, making the implementation simpler and more reliable.

💡 User Tips

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

Implementation Steps

Create Draft PR Ready-for-Review Reminder Bot

This phase implements the complete bot functionality following established repository patterns for PR automation, including the workflow configuration, bot script logic, and required changelog entry.

Task 1: Create GitHub Actions Workflow File

Create the workflow configuration that triggers when commits are pushed to draft PRs with changes requested reviews.

• Create new workflow file at .github/workflows/bot-pr-draft-ready-reminder.yml
• Configure pull_request_target event with types: [synchronize] to detect pushes to PR branches
• Include workflow_dispatch input with pr_number (required) and dry_run (boolean, default: true) for manual testing
• Set minimal permissions: contents: read, pull-requests: write, issues: write
• Add concurrency group keyed on PR number: draft-ready-reminder-${{ github.event.pull_request.number || inputs.pr_number }}
• Include step-security/harden-runner as first step with egress-policy: audit
• Use actions/checkout with ref: main for fork security (standard pattern for pull_request_target)
• Invoke the bot script via actions/github-script action, passing DRY_RUN environment variable
• Pin all action versions with SHA hashes following existing workflow conventions

Task 2: Create Bot Script with Core Logic

Implement the JavaScript module that checks PR conditions and posts the reminder comment idempotently.

• Create new script file at .github/scripts/bot-pr-draft-ready-reminder.js
• Export async function accepting { github, context } following existing module pattern
• Define unique comment marker constant: <!-- draft-ready-reminder-bot -->
• Implement PR data retrieval: get PR number from context or environment, fetch PR details to check draft status
• Implement review decision check using GraphQL query for PullRequest.reviewDecision field
• Add early exit conditions: skip if PR is not draft, skip if review decision is not CHANGES_REQUESTED
• Implement duplicate comment detection: search existing PR comments for the marker, skip if found
• Implement comment posting with the specified format:
  • Marker as first line (HTML comment)
  • Greeting: "Hi @{author}, we noticed your pull request has had recent changes..."
  • Instructions to use /review command or click "Ready for Review" button
  • Team signature consistent with other bots
• Implement dry-run mode: log intended actions without posting when DRY_RUN is true
• Add console logging for debugging: log PR state, review decision, and action taken

Task 3: Add Changelog Entry

Document the new bot workflow in the changelog following project conventions.

• Add entry to CHANGELOG.md under the [Unreleased] section
• Place under the ### Added category
• Use format: - Added GitHub Actions workflow to remind draft PR authors to mark ready for review after pushing changes (#ISSUE_NUMBER)
• Include the issue number in parentheses as required by changelog validation

🤖 Prompt for AI agents

Implement the complete draft PR ready-for-review reminder bot following
established repository patterns for PR automation. This includes creating the
workflow configuration, bot script logic, and changelog entry.

**Workflow Configuration:**
- Create `.github/workflows/bot-pr-draft-ready-reminder.yml`
- Trigger on `pull_request_target` event with `types: [synchronize]` to detect
new commits pushed to PR branches
- Add `workflow_dispatch` input with required `pr_number` and optional `dry_run`
(boolean, default: true) for manual testing
- Set minimal permissions: `contents: read`, `pull-requests: write`, `issues:
write`
- Configure concurrency group: `draft-ready-reminder-${{
github.event.pull_request.number || inputs.pr_number }}`
- Include `step-security/harden-runner` as first step with `egress-policy:
audit`
- Use `actions/checkout` with `ref: main` for fork security
- Invoke bot script via `actions/github-script` action, passing `DRY_RUN`
environment variable
- Pin all action versions with SHA hashes following existing workflow
conventions

**Bot Script Logic:**
- Create `.github/scripts/bot-pr-draft-ready-reminder.js`
- Export async function accepting `{ github, context }` following existing
module pattern
- Define unique comment marker: `<!-- draft-ready-reminder-bot -->`
- Retrieve PR number from context or environment and fetch PR details to check
`draft` status
- Query GraphQL for `PullRequest.reviewDecision` field to check review state
- Implement early exit conditions: skip if PR is not draft OR if review decision
is not `CHANGES_REQUESTED`
- Implement duplicate comment detection by searching existing PR comments for
the marker
- Post comment with format:
  - Marker as first line (HTML comment)
- Greeting: "Hi @{author}, we noticed your pull request has had recent
changes..."
  - Instructions to use `/review` command or click "Ready for Review" button
  - Team signature consistent with other bots
- Support dry-run mode: log intended actions without posting when `DRY_RUN` is
true
- Add console logging for debugging: log PR state, review decision, and action
taken

**Changelog:**
- Add entry to `CHANGELOG.md` under `[Unreleased]` section in `### Added`
category
- Format: `- Added GitHub Actions workflow to remind draft PR authors to mark
ready for review after pushing changes (`#ISSUE_NUMBER`)`

---

🚀 Next Steps

🤖 All AI agent prompts combined

Implement the complete draft PR ready-for-review reminder bot following
established repository patterns for PR automation. This includes creating the
workflow configuration, bot script logic, and changelog entry.

**Workflow Configuration:**
- Create `.github/workflows/bot-pr-draft-ready-reminder.yml`
- Trigger on `pull_request_target` event with `types: [synchronize]` to detect
new commits pushed to PR branches
- Add `workflow_dispatch` input with required `pr_number` and optional `dry_run`
(boolean, default: true) for manual testing
- Set minimal permissions: `contents: read`, `pull-requests: write`, `issues:
write`
- Configure concurrency group: `draft-ready-reminder-${{
github.event.pull_request.number || inputs.pr_number }}`
- Include `step-security/harden-runner` as first step with `egress-policy:
audit`
- Use `actions/checkout` with `ref: main` for fork security
- Invoke bot script via `actions/github-script` action, passing `DRY_RUN`
environment variable
- Pin all action versions with SHA hashes following existing workflow
conventions

**Bot Script Logic:**
- Create `.github/scripts/bot-pr-draft-ready-reminder.js`
- Export async function accepting `{ github, context }` following existing
module pattern
- Define unique comment marker: `<!-- draft-ready-reminder-bot -->`
- Retrieve PR number from context or environment and fetch PR details to check
`draft` status
- Query GraphQL for `PullRequest.reviewDecision` field to check review state
- Implement early exit conditions: skip if PR is not draft OR if review decision
is not `CHANGES_REQUESTED`
- Implement duplicate comment detection by searching existing PR comments for
the marker
- Post comment with format:
  - Marker as first line (HTML comment)
- Greeting: "Hi @{author}, we noticed your pull request has had recent
changes..."
  - Instructions to use `/review` command or click "Ready for Review" button
  - Team signature consistent with other bots
- Support dry-run mode: log intended actions without posting when `DRY_RUN` is
true
- Add console logging for debugging: log PR state, review decision, and action
taken

**Changelog:**
- Add entry to `CHANGELOG.md` under `[Unreleased]` section in `### Added`
category
- Format: `- Added GitHub Actions workflow to remind draft PR authors to mark
ready for review after pushing changes (`#ISSUE_NUMBER`)`

💡 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!

[parvninama]

I’m interested in picking this up — I’ll self-assign and start working on it :)