ultralytics-actions 0.1.2__tar.gz → 0.1.4__tar.gz

{ultralytics_actions-0.1.2 → ultralytics_actions-0.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ultralytics-actions
-Version: 0.1.2
+Version: 0.1.4
 Summary: Ultralytics Actions for GitHub automation and PR management.
 Author-email: Glenn Jocher <glenn.jocher@ultralytics.com>
 Maintainer-email: Ultralytics <hello@ultralytics.com>
@@ -64,8 +64,8 @@ Ultralytics Actions automatically applies formats, updates, and enhancements usi
 - **Spell Check:** Common misspellings are caught using [codespell](https://github.com/codespell-project/codespell).
 - **Broken Links Check:** Broken links in documentation and Markdown files are identified using [Lychee](https://github.com/lycheeverse/lychee).
 - **PR Summary:** Concise Pull Request summaries are generated using [OpenAI](https://openai.com/) GPT-5, improving clarity and review efficiency.
-- **PR Review:** AI-powered inline code reviews identify critical bugs, security issues, and code quality concerns with suggested fixes.
-- **Auto-labeling:** Relevant labels are applied to issues and pull requests via [OpenAI](https://openai.com/) GPT-5 for intelligent categorization.
+- **PR Review:** AI-powered code reviews identify critical bugs, security issues, and code quality concerns with suggested fixes.
+- **Auto-labeling:** Applies relevant labels to issues and PRs via [OpenAI](https://openai.com/) GPT-5 for intelligent categorization.
 
 ## 🛠️ How It Works
 

{ultralytics_actions-0.1.2 → ultralytics_actions-0.1.4}/README.md

@@ -26,8 +26,8 @@ Ultralytics Actions automatically applies formats, updates, and enhancements usi
 - **Spell Check:** Common misspellings are caught using [codespell](https://github.com/codespell-project/codespell).
 - **Broken Links Check:** Broken links in documentation and Markdown files are identified using [Lychee](https://github.com/lycheeverse/lychee).
 - **PR Summary:** Concise Pull Request summaries are generated using [OpenAI](https://openai.com/) GPT-5, improving clarity and review efficiency.
-- **PR Review:** AI-powered inline code reviews identify critical bugs, security issues, and code quality concerns with suggested fixes.
-- **Auto-labeling:** Relevant labels are applied to issues and pull requests via [OpenAI](https://openai.com/) GPT-5 for intelligent categorization.
+- **PR Review:** AI-powered code reviews identify critical bugs, security issues, and code quality concerns with suggested fixes.
+- **Auto-labeling:** Applies relevant labels to issues and PRs via [OpenAI](https://openai.com/) GPT-5 for intelligent categorization.
 
 ## 🛠️ How It Works
 

{ultralytics_actions-0.1.2 → ultralytics_actions-0.1.4}/actions/__init__.py

@@ -23,4 +23,4 @@
 #     ├── test_summarize_pr.py
 #     └── ...
 
-__version__ = "0.1.2"
+__version__ = "0.1.4"

{ultralytics_actions-0.1.2 → ultralytics_actions-0.1.4}/actions/first_interaction.py

@@ -5,12 +5,14 @@ from __future__ import annotations
 import os
 import time
 
+from . import review_pr
 from .utils import Action, filter_labels, get_completion, get_pr_open_response, remove_html_comments
 
 SUMMARY_START = (
     "## 🛠️ PR Summary\n\n<sub>Made with ❤️ by [Ultralytics Actions](https://github.com/ultralytics/actions)<sub>\n\n"
 )
 BLOCK_USER = os.getenv("BLOCK_USER", "false").lower() == "true"
+AUTO_PR_REVIEW = os.getenv("REVIEW", "true").lower() == "true"
 
 
 def apply_and_check_labels(event, number, node_id, issue_type, username, labels, label_descriptions):
@@ -185,6 +187,9 @@ def main(*args, **kwargs):
 
     # Use unified PR open response for new PRs (summary + labels + first comment in 1 API call)
     if issue_type == "pull request" and action == "opened":
+        if event.should_skip_pr_author():
+            return
+
         print("Processing PR open with unified API call...")
         diff = event.get_pr_diff()
         response = get_pr_open_response(event.repository, diff, title, body, label_descriptions)
@@ -192,6 +197,8 @@ def main(*args, **kwargs):
         if summary := response.get("summary"):
             print("Updating PR description with summary...")
             event.update_pr_description(number, SUMMARY_START + summary)
+        else:
+            summary = body
 
         if relevant_labels := response.get("labels", []):
             apply_and_check_labels(event, number, node_id, issue_type, username, relevant_labels, label_descriptions)
@@ -200,6 +207,14 @@ def main(*args, **kwargs):
             print("Adding first interaction comment...")
             time.sleep(1)  # sleep to ensure label added first
             event.add_comment(number, node_id, first_comment, issue_type)
+
+        # Automatic PR review after first interaction
+        if AUTO_PR_REVIEW:
+            print("Starting automatic PR review...")
+            review_number = review_pr.dismiss_previous_reviews(event)
+            review_data = review_pr.generate_pr_review(event.repository, diff, title, summary)
+            review_pr.post_review_summary(event, review_data, review_number)
+            print("PR review completed")
         return
 
     # Handle issues and discussions (NOT PRs)

{ultralytics_actions-0.1.2 → ultralytics_actions-0.1.4}/actions/review_pr.py

@@ -79,34 +79,20 @@ def generate_pr_review(repository: str, diff_text: str, pr_title: str, pr_descri
     diff_truncated = len(diff_text) > limit
     lines_changed = sum(len(lines) for lines in diff_files.values())
 
-    comment_guidance = (
-        "Provide up to 1-3 comments only if critical issues exist"
-        if lines_changed < 50
-        else "Provide up to 3-5 comments only if high-impact issues exist"
-        if lines_changed < 200
-        else "Provide up to 5-10 comments only for the most critical issues"
-    )
-
     content = (
         "You are an expert code reviewer for Ultralytics. Provide detailed inline comments on specific code changes.\n\n"
-        "Focus on: Code quality, style, best practices, bugs, edge cases, error handling, performance, security, documentation, test coverage\n\n"
-        "FORMATTING: Use backticks for all summary and suggestion code, files, branches, functions, variables, packages, e.g. `x=3`\n\n"
+        "Focus on: Bugs, security, performance, best practices, edge cases, error handling\n\n"
+        "FORMATTING: Use backticks for code: `x=3`, `file.py`, `function()`\n\n"
         "CRITICAL RULES:\n"
-        "1. Quality over quantity: Zero comments is fine for clean code - only flag truly important issues\n"
-        f"2. {comment_guidance} - these are maximums, not targets\n"
-        "3. CRITICAL: Do not post separate comments on adjacent/nearby lines (within 10 lines). Combine all related issues into ONE comment\n"
-        "4. When combining issues from multiple lines, use 'start_line' (first line) and 'line' (last line) to highlight the entire range\n"
-        "5. Each comment must reference separate areas - no overlapping line ranges\n"
-        "6. Prioritize: CRITICAL bugs/security > HIGH impact issues > code quality\n"
-        "7. Keep comments concise, friendly, and easy to understand - avoid jargon when possible\n"
-        "8. DO not comment on routine changes: adding imports, adding dependencies, updating version numbers, standard refactoring\n"
-        "9. Trust the developer - only flag issues with clear evidence of problems, not hypothetical concerns\n\n"
-        "SUMMARY GUIDELINES:\n"
-        "- Keep summary brief, clear, and actionable - avoid overly detailed explanations\n"
-        "- Highlight only the most important findings\n"
-        "- Do NOT include file names or line numbers in the summary - inline comments already show exact locations\n"
-        "- Focus on what needs to be fixed, not where\n\n"
-        "CODE SUGGESTIONS:\n"
+        "1. Quality over quantity - zero comments is fine for clean code, only flag truly important issues\n"
+        "2. Combine issues that are directly related to the same problem\n"
+        "3. Use 'start_line' and 'line' to highlight multi-line ranges when issues span multiple lines\n"
+        "4. Prioritize: CRITICAL bugs/security > HIGH impact > code quality improvements\n"
+        "5. Keep comments concise and friendly - avoid jargon\n"
+        "6. Skip routine changes: imports, version updates, standard refactoring\n\n"
+        "SUMMARY:\n"
+        "- Brief and actionable - what needs fixing, not where (locations shown in inline comments)\n\n"
+        "SUGGESTIONS:\n"
         "- ONLY provide 'suggestion' field when you have high certainty the code is problematic AND sufficient context for a confident fix\n"
         "- If uncertain about the correct fix, omit 'suggestion' field and explain the concern in 'message' only\n"
         "- Suggestions must be ready-to-merge code with NO comments, placeholders, or explanations\n"
@@ -118,10 +104,7 @@ def generate_pr_review(repository: str, diff_text: str, pr_title: str, pr_descri
         "Return JSON: "
         '{"comments": [{"file": "exact/path", "line": N, "severity": "HIGH", "message": "...", "suggestion": "..."}], "summary": "..."}\n\n'
         "Rules:\n"
-        "- Only comment on NEW lines (starting with + in diff)\n"
-        "- Use exact file paths from diff (no ./ prefix)\n"
-        "- Line numbers must match NEW file line numbers from @@ hunks\n"
-        "- When '- old' then '+ new', new line keeps SAME line number\n"
+        "- Only NEW lines (+ in diff), exact paths (no ./), correct line numbers from @@ hunks\n"
         "- Severity: CRITICAL, HIGH, MEDIUM, LOW, SUGGESTION\n"
         f"- Files changed: {len(file_list)} ({', '.join(file_list[:10])}{'...' if len(file_list) > 10 else ''})\n"
         f"- Lines changed: {lines_changed}\n"
@@ -142,7 +125,7 @@ def generate_pr_review(repository: str, diff_text: str, pr_title: str, pr_descri
     ]
 
     try:
-        response = get_completion(messages, reasoning_effort="medium")
+        response = get_completion(messages, reasoning_effort="medium", model="gpt-5-codex")
         print("\n" + "=" * 80 + f"\nFULL AI RESPONSE:\n{response}\n" + "=" * 80 + "\n")
 
         json_str = re.search(r"```(?:json)?\s*(\{.*?\})\s*```", response, re.DOTALL)
@@ -241,12 +224,12 @@ def post_review_summary(event: Action, review_data: dict, review_number: int) ->
     body = (
         f"## {review_title}\n\n"
         "<sub>Made with ❤️ by [Ultralytics Actions](https://github.com/ultralytics/actions)</sub>\n\n"
-        f"{review_data.get('summary', 'Review completed')}\n\n"
+        f"{review_data.get('summary', 'Review completed')[:1000]}\n\n"  # Clip summary length
     )
 
     if comments:
         shown = min(len(comments), 10)
-        body += f"💬 Posted {shown} inline comment{'s' if shown != 1 else ''}{' (10 shown, more available)' if len(comments) > 10 else ''}\n"
+        body += f"💬 Posted {shown} inline comment{'s' if shown != 1 else ''}\n"
 
     if review_data.get("diff_truncated"):
         body += "\n⚠️ **Large PR**: Review focused on critical issues. Some details may not be covered.\n"
@@ -256,14 +239,15 @@ def post_review_summary(event: Action, review_data: dict, review_number: int) ->
 
     # Build inline comments for the review
     review_comments = []
-    for comment in comments[:10]:
+    for comment in comments[:10]:  # Limit to 10 comments
         if not (file_path := comment.get("file")) or not (line := comment.get("line", 0)):
             continue
 
         severity = comment.get("severity", "SUGGESTION")
-        comment_body = f"{EMOJI_MAP.get(severity, '💭')} **{severity}**: {comment.get('message', '')}"
+        comment_body = f"{EMOJI_MAP.get(severity, '💭')} **{severity}**: {comment.get('message', '')[:1000]}"
 
         if suggestion := comment.get("suggestion"):
+            suggestion = suggestion[:1000]  # Clip suggestion length
             if "```" not in suggestion:
                 # Extract original line indentation and apply to suggestion
                 if original_line := review_data.get("diff_files", {}).get(file_path, {}).get(line):
@@ -307,12 +291,15 @@ def main(*args, **kwargs):
         print(f"Skipping: PR state is {event.pr.get('state') if event.pr else 'None'}")
         return
 
+    # Skip self-authored or bot PRs unless manually review_requested
+    if event.event_data.get("action") != "review_requested" and event.should_skip_pr_author():
+        return
+
     print(f"Starting PR review for #{event.pr['number']}")
     review_number = dismiss_previous_reviews(event)
 
     diff = event.get_pr_diff()
-    pr_description = event._pr_summary_cache or event.pr.get("body", "")
-    review = generate_pr_review(event.repository, diff, event.pr.get("title", ""), pr_description)
+    review = generate_pr_review(event.repository, diff, event.pr.get("title", ""), event.pr.get("body", ""))
 
     post_review_summary(event, review, review_number)
     print("PR review completed")

{ultralytics_actions-0.1.2 → ultralytics_actions-0.1.4}/actions/utils/github_utils.py

@@ -188,6 +188,20 @@ class Action:
         """Checks if a user is a member of the organization."""
         return self.get(f"{GITHUB_API_URL}/orgs/{self.repository.split('/')[0]}/members/{username}").status_code == 204
 
+    def should_skip_pr_author(self) -> bool:
+        """Checks if PR should be skipped based on author (self-authored or bot PRs)."""
+        if not self.pr:
+            return False
+        if pr_author := self.pr.get("user", {}).get("login"):
+            if pr_author == self.get_username():
+                print(f"Skipping: PR author ({pr_author}) is the same as bot")
+                return True
+            # Check both user.type and [bot] suffix for robust bot detection
+            if self.pr.get("user", {}).get("type") == "Bot" or pr_author.endswith("[bot]"):
+                print(f"Skipping: PR author ({pr_author}) is a bot")
+                return True
+        return False
+
     def is_fork_pr(self) -> bool:
         """Checks if PR is from a fork (different repo than base)."""
         if not self.pr:
@@ -267,10 +281,10 @@ class Action:
         start = "## 🛠️ PR Summary"
         if start in description:
             print("Existing PR Summary found, replacing.")
-            updated_description = description.split(start)[0] + new_summary
+            updated_description = description.split(start)[0].rstrip() + "\n\n" + new_summary
         else:
             print("PR Summary not found, appending.")
-            updated_description = description + "\n\n" + new_summary
+            updated_description = (description.rstrip() + "\n\n" + new_summary) if description.strip() else new_summary
 
         self.patch(url, json={"body": updated_description})
         self._pr_summary_cache = new_summary
@@ -386,7 +400,7 @@ Thank you 🙏
         try:
             data = response.json()["data"]["repository"]["pullRequest"]
             comments = data["reviews"]["nodes"] + data["comments"]["nodes"]
-            token_username = self.get_username()
+            username = self.get_username()
             author = data["author"]["login"] if data["author"]["__typename"] != "Bot" else None
 
             contributors = {x["author"]["login"] for x in comments if x["author"]["__typename"] != "Bot"}
@@ -399,10 +413,10 @@ Thank you 🙏
                             contributors.add(login)
 
             contributors.discard(author)
-            contributors.discard(token_username)
+            contributors.discard(username)
 
             pr_credit = ""
-            if author and author != token_username:
+            if author and author != username:
                 pr_credit += f"@{author}"
             if contributors:
                 pr_credit += (" with contributions from " if pr_credit else "") + ", ".join(

{ultralytics_actions-0.1.2 → ultralytics_actions-0.1.4}/actions/utils/openai_utils.py

@@ -112,6 +112,7 @@ def get_completion(
     temperature: float = 1.0,
     reasoning_effort: str = None,
     response_format: dict = None,
+    model: str = OPENAI_MODEL,
 ) -> str | dict:
     """Generates a completion using OpenAI's Responses API based on input messages."""
     assert OPENAI_API_KEY, "OpenAI API key is required."
@@ -122,8 +123,8 @@ def get_completion(
 
     max_retries = 2
     for attempt in range(max_retries + 2):
-        data = {"model": OPENAI_MODEL, "input": messages, "store": False, "temperature": temperature}
-        if "gpt-5" in OPENAI_MODEL:
+        data = {"model": model, "input": messages, "store": False, "temperature": temperature}
+        if "gpt-5" in model:
             data["reasoning"] = {"effort": reasoning_effort or "low"}
             # GPT-5 Responses API handles JSON via prompting, not format parameter
 

{ultralytics_actions-0.1.2 → ultralytics_actions-0.1.4}/ultralytics_actions.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ultralytics-actions
-Version: 0.1.2
+Version: 0.1.4
 Summary: Ultralytics Actions for GitHub automation and PR management.
 Author-email: Glenn Jocher <glenn.jocher@ultralytics.com>
 Maintainer-email: Ultralytics <hello@ultralytics.com>
@@ -64,8 +64,8 @@ Ultralytics Actions automatically applies formats, updates, and enhancements usi
 - **Spell Check:** Common misspellings are caught using [codespell](https://github.com/codespell-project/codespell).
 - **Broken Links Check:** Broken links in documentation and Markdown files are identified using [Lychee](https://github.com/lycheeverse/lychee).
 - **PR Summary:** Concise Pull Request summaries are generated using [OpenAI](https://openai.com/) GPT-5, improving clarity and review efficiency.
-- **PR Review:** AI-powered inline code reviews identify critical bugs, security issues, and code quality concerns with suggested fixes.
-- **Auto-labeling:** Relevant labels are applied to issues and pull requests via [OpenAI](https://openai.com/) GPT-5 for intelligent categorization.
+- **PR Review:** AI-powered code reviews identify critical bugs, security issues, and code quality concerns with suggested fixes.
+- **Auto-labeling:** Applies relevant labels to issues and PRs via [OpenAI](https://openai.com/) GPT-5 for intelligent categorization.
 
 ## 🛠️ How It Works