Skip to content

Bug: Assignment workflow treats mergeable PRs as merged #149

@SarthakJagota

Description

@SarthakJagota

Is there an existing issue for this?

  • I have searched the existing issues

What happened?

.

🔍 Issue Overview

The assignment workflow currently determines whether a pull request is merged by calling the GET /pulls/{pull_number}/merge endpoint and checking for a 204 status code.

However, this endpoint only indicates whether a pull request is mergeable, not whether it has actually been merged. As a result, open but mergeable pull requests can be incorrectly treated as completed.

🎯 Impact

This can lead to incorrect issue assignment behavior, where contributors may be allowed or blocked from taking new issues based on an inaccurate merge status.

✅ Expected Behavior

Only pull requests that have actually been merged should be treated as completed when validating active issue assignments.

🔧 Suggested Fix

Fetch pull request details using GET /pulls/{pull_number} and determine merge completion by checking the merged field in the response.

A pull request has already been opened to address this issue: #<PR_NUMBER>

(Replace <PR_NUMBER> after creating the PR.)

Record

  • I agree to follow this project's Code of Conduct
  • I want to work on this issue

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions