Skip to content

Conversation

nikolapeja6
Copy link
Member

The functionality for list_pull_requests_by_repo and list_pull_requests_by_project is similar, the only difference being the API that is called under the hood. Now, both APIs are merged into a single tool, that requires either project or repo.

GitHub issue number

none

Associated Risks

none

PR Checklist

  • I have read the contribution guidelines
  • I have read the code of conduct guidelines
  • Title of the pull request is clear and informative.
  • 👌 Code hygiene
  • 🔭 Telemetry added, updated, or N/A
  • 📄 Documentation added, updated, or N/A
  • 🛡️ Automated tests added, or N/A

🧪 How did you test it?

Tested manually with the scenarios:

  • calling tool with only repo
  • calling tool with only projct
  • calling tool without repo or project
  • calling tool with both repo and project

@nikolapeja6 nikolapeja6 requested a review from a team as a code owner October 9, 2025 15:43
Copy link

github-actions bot commented Oct 9, 2025

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@nikolapeja6 nikolapeja6 merged commit 803b663 into main Oct 9, 2025
7 checks passed
@nikolapeja6 nikolapeja6 deleted the users/nikolapeja6/merge-repo-tools-1-listing-prs branch October 9, 2025 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants