-
Notifications
You must be signed in to change notification settings - Fork 320
Sync eng/common directory with azure-sdk-tools for PR 13005 #3371
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
Open
azure-sdk
wants to merge
14
commits into
main
Choose a base branch
from
sync-eng/common-djurek/codeowners-ci-work-item-spec-repo-path-13005
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+29
−2
Open
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
81df701
Add field for Spec Project Path property
danieljurek d129e47
Reorder properties
danieljurek fc1cf75
Cleanup
danieljurek 5a78fc1
Logging
danieljurek 754b709
Move SpecProjectPath into Package-Properties.ps1
danieljurek 00d6656
Update SpecProjectPath
danieljurek 7f8ad8a
Fix accidental removal of $title
danieljurek 8c27a4b
Create or update with SpecProjectPath
danieljurek 770bfcb
Revert logic, cannot test
danieljurek 8dfc1a9
Revert logic, cannot test
danieljurek 2f6361f
Revert irrelevant file
danieljurek 95fbddd
Retain title
danieljurek af30bf7
Review feedback
danieljurek 5bd0b7a
Review feedback
danieljurek 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
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.
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.
The condition
(!$workItem.fields.ContainsKey('Custom.SpecProjectPath') -and $packageInfo.SpecProjectPath)may not work as intended in PowerShell. When$packageInfo.SpecProjectPathis an empty string (the default value from the parameter), PowerShell will treat it as falsy, but you likely want to update the work item only when there's a non-empty value.Consider using a more explicit check:
This ensures that empty strings from the default parameter value don't trigger unnecessary updates.