Update merge-main-into-prs.yml
diff --git a/.github/workflows/merge-main-into-prs.yml b/.github/workflows/merge-main-into-prs.yml
index 06757d3f194..9ed945c7897 100644
--- a/.github/workflows/merge-main-into-prs.yml
+++ b/.github/workflows/merge-main-into-prs.yml
@@ -45,12 +45,10 @@ jobs:
         for pr in open_pulls:
             # Compare PR head with main to see if it's behind
             try:
-                comparison = repo.compare(pr.base.ref, pr.head.ref)  # Ensure correct order of base and head
-                if comparison.behind_by > 0:
-                    # Merge main into the PR branch
-                    success = pr.update_branch()
-                    assert success, "Branch update failed"
-                    print(f"Merged 'master' into PR #{pr.number} ({pr.head.ref}) successfully.")
+                # Merge main into the PR branch
+                success = pr.update_branch()
+                assert success, "Branch update failed"
+                print(f"Merged 'master' into PR #{pr.number} ({pr.head.ref}) successfully.")
             except Exception as e:
                 print(f"Could not merge 'master' into PR #{pr.number} ({pr.head.ref}): {e}")
       env:

<!--
Thank you 🙏 for your contribution to [Ultralytics](https://ultralytics.com) 🚀! Your effort in enhancing our repositories is greatly appreciated. To streamline the process and assist us in integrating your Pull Request (PR) effectively, please follow these steps:

1. **Check for Existing Contributions**: Before submitting, kindly explore existing PRs to ensure your contribution is unique and complementary.
2. **Link Related Issues**: If your PR addresses an open issue, please link it in your submission. This helps us better understand the context and impact of your contribution.
3. **Elaborate Your Changes**: Clearly articulate the purpose of your PR. Whether it's a bug fix or a new feature, a detailed description aids in a smoother integration process.
4. **Ultralytics Contributor License Agreement (CLA)**: To uphold the quality and integrity of our project, we require all contributors to sign the CLA. Please confirm your agreement by commenting below:

    _I have read the CLA Document and I sign the CLA_

For more detailed guidance and best practices on contributing, refer to our ✅ [Contributing Guide](https://docs.ultralytics.com/help/contributing). Your adherence to these guidelines ensures a faster and more effective review process.
--->


## 🛠️ PR Summary

<sub>Made with ❤️ by [Ultralytics Actions](https://github.com/ultralytics/actions)<sub>

### 🌟 Summary
Streamlining GitHub Actions to Automatically Update PR Branches 🚀

### 📊 Key Changes
- **Simplified the process** for merging the main branch into PR branches directly, without checking if the PR is behind the main branch first.
- **Removed comparison checks** between PR head and main, which previously determined if a PR was lagging behind the main branch.

### 🎯 Purpose & Impact
- **Smoother Workflow:** By always attempting to merge the main branch into open PRs, this change ensures that PRs are consistently up-to-date, making the integration process smoother.
- **Increased Efficiency:** Removes the need to compare branches, potentially speeding up the workflow execution time.
- **Potential Risk:** There's a slight risk of merge conflicts or issues in PR branches if they're automatically updated without prior checks, but this approach keeps all contributions aligned with the latest main branch changes.

Overall, this update aims to make developers' lives easier by automating housekeeping tasks, though users should be aware and manage potential merge conflicts proactively.