Skip to content
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

Fix create-pull-request bug #1131

Merged
1 commit merged into from
Oct 22, 2020

Conversation

@chidozieononiwu chidozieononiwu requested a review from a team as a code owner October 21, 2020 22:50
@chidozieononiwu chidozieononiwu force-pushed the bugfix/CommonPullRequestScript branch from 0c9fdce to dc3a505 Compare October 21, 2020 22:57
@azure-sdk
Copy link
Collaborator

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

@chidozieononiwu chidozieononiwu force-pushed the bugfix/CommonPullRequestScript branch from dc3a505 to 60b4768 Compare October 21, 2020 23:53
@azure-sdk
Copy link
Collaborator

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

@chidozieononiwu chidozieononiwu force-pushed the bugfix/CommonPullRequestScript branch from 60b4768 to 742593d Compare October 22, 2020 06:17
@azure-sdk
Copy link
Collaborator

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

@@ -86,4 +86,4 @@ steps:
-UserReviewers "${{ parameters.GHReviewersVariable }}"
-TeamReviewers "${{ parameters.GHTeamReviewersVariable }}"
-Assignees "${{ parameters.GHAssignessVariable }}"
-CloseAfterOpenForTesting $${{ parameters.CloseAfterOpenForTesting }}
-CloseAfterOpenForTesting $${{ coalesce(parameters.CloseAfterOpenForTesting, 'false') }}
Copy link
Member

Choose a reason for hiding this comment

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

Do we need to coalesce given that we default the value to false?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, unless we go set it for all the ci.yml files. Other wise it will resolve to ' ' at times.

Copy link
Member

Choose a reason for hiding this comment

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

I'm fine with this change but I am curious what cases would hit this with empty? A pointer would be good.

Copy link
Member Author

Choose a reason for hiding this comment

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

So for regular non-test pipelines. Where no parameter is passed to TestPipeline the value here will resolve to ' '

Copy link
Member

Choose a reason for hiding this comment

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

Why is that? I see on line 22 https://github.com/Azure/azure-sdk-tools/pull/1131/files#diff-2da9c3d63f1a3177d12f9e47cb7a8d973239379a5e86970b335825f663e6c4f1L22 we pass false as a default value so it should be false if nothing is passed.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes, but if you pass a value to this the default will be overridden. So if when ${{ parameter.TestPipeline }} is passed it will override this default value. Right? And in some case that value may resolve to an empty string "".

Copy link
Member

@weshaggard weshaggard left a comment

Choose a reason for hiding this comment

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

This change looks good however I do believe it will require some changes in the language repos as well, which I think I saw some PRs for already but I just wanted to call that out as we need to get those merged closely after this.

@chidozieononiwu chidozieononiwu force-pushed the bugfix/CommonPullRequestScript branch from 742593d to 6f98b34 Compare October 22, 2020 20:42
@azure-sdk
Copy link
Collaborator

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

@@ -35,7 +35,7 @@ function Invoke-GitHubAPIPost {
else {
$warning = "{0} with Uri [ $apiURI ] did not fire request because of empty body." -f (Get-PSCallStack)[1].FunctionName
LogWarning $warning
exit 0
return $null
Copy link
Member

Choose a reason for hiding this comment

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

I'm ok with this but what prompted this? I'd still like us to fix the callers to not have us ever hit this empty body case.

@ghost
Copy link

ghost commented Oct 22, 2020

Hello @azure-sdk!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@chidozieononiwu
Copy link
Member Author

/check-enforcer override

This pull request was closed.
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.

4 participants