Skip to content

Conversation

@raych1
Copy link
Member

@raych1 raych1 commented Nov 22, 2025

@raych1 raych1 requested a review from a team as a code owner November 22, 2025 00:30
Copilot AI review requested due to automatic review settings November 22, 2025 00:30
Copilot finished reviewing on behalf of raych1 November 22, 2025 00:32
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes an issue where API review requests for Java packages weren't including the groupId in the package name. The change ensures that when a package has a groupId (primarily for Java packages), the API review request uses the format groupId:packageName instead of just the package name.

Key Changes

  • Modified the Submit-Request function to accept and use a group parameter
  • Added logic to construct a full package name with groupId when available
  • Updated the function call to pass the packageInfo.Group field

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
eng/common/scripts/Detect-Api-Changes.ps1 Added group parameter to Submit-Request function and logic to construct full package name with groupId; also includes trailing whitespace fix on line 83
eng/common/pipelines/templates/steps/validate-all-packages.yml Added explanatory comment for PackageInfoFiles parameter
eng/common/pipelines/templates/steps/create-apireview.yml Added explanatory comment for PackageInfoFiles parameter
Comments suppressed due to low confidence (1)

eng/common/scripts/Detect-Api-Changes.ps1:36

  • The $reviewFileName is still using $packageName instead of $fullPackageName. This could cause inconsistencies when the group is present, as the query parameter uses $fullPackageName but the review file name uses the ungrouped $packageName. Consider whether the review file name should also include the group, or if this is intentional. If groupId should be included in the filename, use $fullPackageName here.
    $reviewFileName = "$($packageName)_$($LanguageShort).json"

$query.Add('repoName', $repoName)
$query.Add('pullRequestNumber', $PullRequestNumber)
$query.Add('packageName', $packageName)
$query.Add('packageName', $fullPackageName)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@praveenkuttappan can we merge this change directly or any change needs to make in API view server side?

CC: @helen229 @AlitzelMendez

@azure-sdk
Copy link
Collaborator

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🔬 Dev in PR

Development

Successfully merging this pull request may close these issues.

Update APIReview scripts to use full name for Java libraries

3 participants