-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Repo sync for protected CLA branch #6207
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
Conversation
…o-docs-pr into 1767836-damabe2
…o-docs-pr into 1767836-damabe2
…o-docs-pr into 1767836-damabe2
…o-docs-pr into 1767836-damabe2
…o-docs-pr into 1767836-damabe2
…o-docs-pr into 1767836-damabe2
We don't want to call Team Explorer 'legacy' yet as that has a negative connotation to it. We've had instances of customers reacting badly to it, since Team Explorer is still used for TFVC and some Azure DevOps integrations.
Removed the term 'legacy' when referring to Team Explorer
C# console tutorial: Part 2 only applies to VS 2019
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)
minor text edit
Co-authored-by: Gordon Hogenson <[email protected]>
Adjust console tutorial TOC for VS 2017
AddDescriptionMetadata: User Story 1767836
Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows: |
The pull request is created from master637436536690199627 to master to fix git push error for protected CLA branch