-
Notifications
You must be signed in to change notification settings - Fork 5.8k
TypeSpec pipeline adjustment #24826
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
TypeSpec pipeline adjustment #24826
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
24b17cc
TypeSpec pipeline adjustment
ckairen 2d36e52
adding root repo files
ckairen 0f06486
testing
ckairen 81d06ba
revert testing
ckairen 780113f
windows separator
ckairen abfa00a
Merge branch 'main' into al/tsp-pipeline
mikeharder 0c03c5b
Add debugging
mikeharder cb946e2
Fix typo
mikeharder 9a04aef
Null check
mikeharder a09312b
Null check
mikeharder f5bc8dd
Temporarily disable git revert
mikeharder 2464da9
Debug
mikeharder 2084330
Fix typos
mikeharder 44c7802
Revert git changes
mikeharder ead9873
Remove debug
mikeharder a2112ec
Rename "changed specs" to "impacted specs"
mikeharder 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
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.
Are there cases where $_ is empty/null?
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.
Yes, all of the null checks in this PR were added to fix bugs we found in testing. It might be possible to refactor/rewrite the powershell code to be cleaner, but we wanted to get this merged in and working quickly. I don't understand exactly how PowerShell handles null/empty string, and it seems to be different depending which API you are using.
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.
I believe
$_was empty/null specifically in the case where there was no git diff (e.g. a PR with no changes).