Updated message that displays in terminal when codeflash creates a PR

[zomglings]

PR Type

Enhancement

---

Description

• Extract PR number into variable

• Construct full PR URL string

• Include PR URL in success log message

---

Changes walkthrough 📝

	Relevant files
Enhancement	create_pr.py Include PR URL in creation log                                                      codeflash/result/create_pr.py Added pr_number variable from response.text Constructed pr_url using owner and repo Updated logger.info to display PR URL +3/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about PR-Agent usage.

Check out the documentation for more information.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Response format handling response.text may include leading/trailing whitespace or unexpected content. Consider stripping and validating it before using it as the PR number in the URL. pr_number = response.text pr_url = f"https://github.com/{owner}/{repo}/pull/{pr_number}" logger.info(f"Successfully created a new PR #{pr_number} with the optimized code: {pr_url}") Variable scope Verify that owner and repo are defined and correctly set in this scope to prevent NameError when constructing the PR URL. pr_number = response.text pr_url = f"https://github.com/{owner}/{repo}/pull/{pr_number}" logger.info(f"Successfully created a new PR #{pr_number} with the optimized code: {pr_url}")

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Parse PR number from JSON GitHub API responses typically return JSON, so extracting the PR number via response.json() is more robust than relying on raw text. This also avoids parsing errors if the API response format changes. codeflash/result/create_pr.py [135] -pr_number = response.text +data = response.json() +pr_number = data.get("number") Suggestion importance[1-10]: 8 __ Why: Using response.json() is more reliable because GitHub returns structured JSON, preventing parsing errors if the API response format changes.	Medium
General	Use parameterized logging Switch to parameterized logging to defer string interpolation when the log level is disabled and to avoid potential injection risks in log output. codeflash/result/create_pr.py [137] -logger.info(f"Successfully created a new PR #{pr_number} with the optimized code: {pr_url}") +logger.info( + "Successfully created a new PR #%s with the optimized code: %s", + pr_number, + pr_url +) Suggestion importance[1-10]: 6 __ Why: Parameterized logging defers interpolation and mitigates injection risks, improving performance and safety with low implementation overhead.	Low
	Escape URL path segments Use urllib.parse.quote to escape owner and repo components, ensuring the URL is valid even if they contain special characters. This prevents malformed links. codeflash/result/create_pr.py [136] -pr_url = f"https://github.com/{owner}/{repo}/pull/{pr_number}" +from urllib.parse import quote +pr_url = f"https://github.com/{quote(owner)}/{quote(repo)}/pull/{pr_number}" Suggestion importance[1-10]: 4 __ Why: Percent-encoding owner and repo ensures valid URLs but GitHub repository names rarely include special characters, so this offers only a minor benefit.	Low