Skip to content

Repo sync for protected CLA branch #6906

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 20 commits into from
Aug 4, 2021
Merged

Repo sync for protected CLA branch #6906

merged 20 commits into from
Aug 4, 2021

Conversation

ghogen
Copy link
Collaborator

@ghogen ghogen commented Jul 28, 2021

The pull request is created from master637631102313231424 to master to fix git push error for protected CLA branch

ghogen and others added 20 commits July 21, 2021 11:08
* add Note about new Trust Settings in VS2022

* update page ownership metadata

* fix version moniker tag

* minor text edit

* remove unnecessary version monikers

* revise the moniker versioning

* fix build errors

* fix moniker-end tags
Using the DTE2 fixes most issues with the DTE and _DTE. I added a small line mentioning that
* update new dialog for 2019 and NET 5.0

* Update dialog image for 2019 and NET 5.0

* Update container-tools.md

* update filename for pattern

* rename and set outline

* set outline
* Remove file that is producing warnings

* Remove toc
* switch title to sentence caps

* add VS2022 relnotes to TOC
* Move support link in admin-responsibilities.md

* Remove blank lines from admin-roles.md

* Move support link in assign-license-bulk.md

Co-authored-by: Evan Windom (Red Door Collaborative LLC) <[email protected]>
* Drafted ASP.NET Core with React

* edits

* fixed warnings

* Drafted ASP.NET Core Angular app

* updated art

* minor edits

* TOC edits

* fixed blocking issues

* fixed blocking issues

* fixed blocking issues

* toc fixes

* Update docs/javascript/tutorial-asp-net-core-with-angular.md

Co-authored-by: Genevieve Warren <[email protected]>

* Update docs/javascript/tutorial-asp-net-core-with-react.md

Co-authored-by: Genevieve Warren <[email protected]>

Co-authored-by: Genevieve Warren <[email protected]>
* add new screenshot for VS2022 warning msg

* update image link info
* F1 keyword edits

* tweak

* tweak

* tweak
* add vs.find keyword to Find in Files per PM request

* add VS2017 & VS2019 updates

* add screenshots

* delete duplicate vs.findreplace.findinfiles keyword.

* add and revise screenshots

* add more monikers to disambiguate versioned features

* delete Warning note

* rearrange some text to follow different UI between versions

* fix Build error

* add more VS2019-specific content

* add info about checkboxes under Look In section

* revise list of locations in the Look In section

* revise exclude from search info

* remove superfluous Look In info from VS2019 content

* final formatting edits

* fix moniker range to show VS2019 sections in VS2022
* F1 keyword edits

* tweak

* tweak

* tweak

* unit testing updates

* freshness checks

* freshness checks
* Broken link fixed.

* Suggestion updated.
* F1 keyword edits

* tweak

* tweak

* tweak

* unit testing updates

* freshness checks

* freshness checks

* Updated freshness
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)
@PRMerger8
Copy link
Contributor

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver
Copy link
Contributor

ktoliver commented Aug 3, 2021

@ghogen @Mikejo5000 I don't know what a protected CLA branch is, but I see two PRs to sync it in this repository. The PRs are 6 and 5 days old. Shall I merge them? This PR and #6909.

.

@ghogen
Copy link
Collaborator Author

ghogen commented Aug 3, 2021

@ktoliver Hmm, these should be merged, but we should not use squash merge for it. I think these used to be merged automatically by the repo sync process, but probably when I changed the branch settings to enforce squash merge, these could no longer merge successfully. I will have to decide whether to change the branch settings again to allow it, or merge these manually. I think for now, I'll change the branch settings and we will discuss it and decide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.