Skip to content

Conversation

@carlossanlop
Copy link
Contributor

Creating this PR manually because dotnet-maestro-bot is not being nice and is refusing to refresh the automated PR with the branding commit from the base release branch: #84336

I'll close the automated PR after merging this one, if no one objects to this workaround.

dotnet-maestro bot and others added 4 commits March 23, 2023 17:34
…23.1 (#83860)

Microsoft.NET.Workload.Emscripten.net6.Manifest-7.0.100 , Microsoft.NET.Workload.Emscripten.net7.Manifest-7.0.100
 From Version 7.0.4 -> To Version 7.0.5

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…05.1 (#84361)

Microsoft.NET.Workload.Emscripten.net6.Manifest-7.0.100 , Microsoft.NET.Workload.Emscripten.net7.Manifest-7.0.100
 From Version 7.0.5 -> To Version 7.0.6

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
@ghost
Copy link

ghost commented Apr 7, 2023

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

Creating this PR manually because dotnet-maestro-bot is not being nice and is refusing to refresh the automated PR with the branding commit from the base release branch: #84336

I'll close the automated PR after merging this one, if no one objects to this workaround.

Author: carlossanlop
Assignees: carlossanlop
Labels:

area-Infrastructure

Milestone: -

@carlossanlop
Copy link
Contributor Author

Hmm... I think I should submit this PR from a snapped branch, not from release/7.0 directly. Otherwise I don't know what would happen with the merge conflict resolution.

@ghost ghost locked as resolved and limited conversation to collaborators May 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants