-
Notifications
You must be signed in to change notification settings - Fork 4
Add source project key to migration reports #483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Edge Case: Failed source-key lookup collides on duplicate project names
attachFailedSourceKeysbuildskeyByNamekeyed solely on the project name (def.NameField) and then assignsitems[i].SourceKeyby name match. Unlike the Succeeded/Skipped paths (which read the source key directly from the same record), Failed rows are matched purely by name. Project names are not guaranteed unique — the same name can exist across different organizations, or even be reused — so the map silently overwrites earlier entries (last-write-wins). When two projects share a name but have different source keys, a failed row can be annotated with the wrong source key, which is misleading in a migration audit report. Consider disambiguating the lookup by including the organization (the analysisReportRowcarriesOrganization, andgenerateProjectMappingsrows carrysonarcloud_org_key/sonarqube_org_key), or otherwise handling the collision case rather than blindly overwriting.Key the lookup by organization + name so projects that share a name across organizations are not conflated.:
Was this helpful? React with 👍 / 👎