-
Notifications
You must be signed in to change notification settings - Fork 10.6k
[automated] Merge branch 'release/2.2' => 'master' #12444
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
[automated] Merge branch 'release/2.2' => 'master' #12444
Conversation
Fixes https://github.com/aspnet/AspNetCore-Internal/issues/2826 We [use `?.` in `master`](https://github.com/aspnet/AspNetCore/blob/f56cb72b7fa01ea09c3d3b128aaeb9cee937b371/src/Hosting/Server.IntegrationTesting/src/Deployers/ApplicationDeployer.cs#L103) and it seems like the test can end up in this state (by the linked issue) so back-porting that defensive measure seems reasonable.
aaa9305 to
fd5517f
Compare
|
@anurse your comments in the 2.2 commit indicate this fix is already in 'master'. So, why did the merge change anything? |
|
Bump @anurse |
|
I couldn't say. Looking at the file in Seems like a git diff quirk to me. |
|
/azp run AspNetCore-ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run AspNetCore-helix-test |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
This pull request has been updated. This PR merges commits made on release/2.2 by the following committers: |
|
@jkotalik can you take a look at the conflicts when you have a few minutes? I'm not terribly surprised to see conflicts here |
|
This pull request has been updated. This PR merges commits made on release/2.2 by the following committers: |
|
These instructions for merging don't work... Apologies to everyone who got added for no reason. |
344c77b to
94a2755
Compare
94a2755 to
8cbc76f
Compare
|
There we go. That last line should definitely be a force push. IIRC I tried to make a fix for this in arcade but no one reviewed it so I closed it. |
|
Huh? I have been able to update these types of PRs without push -f. Why do you think that is required? |
JunTaoLuo
left a comment
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 changes are what I expect (for my change in 2.1 merging forward at least) though I'm curious why you had to force push.
It avoids a double merge, right? |
|
Yeah I believe @halter73 is correct. I've never had these instructions work for me on the first try. |
I detected changes in the release/2.2 branch which have not been merged yet to master. I'm a robot and am configured to help you automatically keep master up to date, so I've opened this PR.
This PR merges commits made on release/2.2 by the following committers:
Instructions for merging from UI
This PR will not be auto-merged. When pull request checks pass, complete this PR by creating a merge commit, not a squash or rebase commit.
If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.
Instructions for merging via command line
Run these commands to merge this pull request from the command line.
or if you are using SSH
After PR checks are complete push the branch
Instructions for resolving conflicts
Instructions for updating this pull request
Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/2.2-to-master'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
or if you are using SSH
Contact .NET Core Engineering if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.