-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Use googletest's new 'main' branch #38409
Conversation
'main' is the default branch in dotnet/googletest now. We'll need this in our servicing branches except release/2.1. @mmitche @wtgodbe to conform: Those branches all remain open 'til EOD today❔ In any case, I'm opening the backport PRs. Note there isn't really a rush to complete this today. It's just better if we don't have to do the work later, when we realize the submodule isn't keeping up anymore. |
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/aspnetcore/actions/runs/1463970064 |
@dougbu backporting to release/6.0 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Use googletest's new 'main' branch
Using index info to reconstruct a base tree...
M .gitmodules
M src/submodules/googletest
Falling back to patching base and 3-way merge...
Failed to merge submodule src/submodules/googletest (not checked out)
Auto-merging src/submodules/googletest
CONFLICT (submodule): Merge conflict in src/submodules/googletest
Auto-merging .gitmodules
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Use googletest's new 'main' branch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
- backport of dotnet#38409 due to submodule conflicts
…due to submodule conflicts
…due to submodule conflicts
- backport of #38409 due to submodule conflicts
No description provided.