Rename to main (#91)

microsoft · May 13, 2021 · 90f1fd6 · 90f1fd6
1 parent 33e9468
commit 90f1fd6
Show file tree

Hide file tree

Showing 4 changed files with 17 additions and 17 deletions.
diff --git a/README.md b/README.md
@@ -4,16 +4,16 @@ Welcome to the repository which contains content for the Microsoft Test Framewor
 MSTest V2 API documentation is available [here](https://docs.microsoft.com/en-us/dotnet/api/microsoft.visualstudio.testtools.unittesting).
 
 ### Documentation
- - [Framework Extensibility Trait Attributes](https://github.com/Microsoft/testfx-docs/blob/master/RFCs/001-Framework-Extensibility-Trait-Attributes.md)
- - [Framework Extensibility for Custom Assertions](https://github.com/Microsoft/testfx-docs/blob/master/RFCs/002-Framework-Extensibility-Custom-Assertions.md)
- - [Customize Running tests](https://github.com/Microsoft/testfx-docs/blob/master/RFCs/003-Customize-Running-Tests.md)
- - [In-assembly parallel execution](https://github.com/Microsoft/testfx-docs/blob/master/RFCs/004-In-Assembly-Parallel-Execution.md)
- - [Framework Extensibility for Custom Test Data Source](https://github.com/Microsoft/testfx-docs/blob/master/RFCs/005-Framework-Extensibility-Custom-DataSource.md)
- - [DynamicData Attribute for Data Driven Tests](https://github.com/Microsoft/testfx-docs/blob/master/RFCs/006-DynamicData-Attribute.md)
- - [DataSource Attribute Vs ITestDataSource](https://github.com/Microsoft/testfx-docs/blob/master/RFCs/007-DataSource-Attribute-VS-ITestDataSource.md)
- - [Test case timeout via runsettings](https://github.com/Microsoft/testfx-docs/blob/master/RFCs/008-TestCase-Timeout.md)
- - [Deltas from MSTest V1](https://github.com/Microsoft/testfx-docs/blob/master/docs/deltaWithMSTestV1.md)
- - [Release Roadmap](https://github.com/Microsoft/testfx-docs/blob/master/docs/releases.md)
+ - [Framework Extensibility Trait Attributes](https://github.com/Microsoft/testfx-docs/blob/main/RFCs/001-Framework-Extensibility-Trait-Attributes.md)
+ - [Framework Extensibility for Custom Assertions](https://github.com/Microsoft/testfx-docs/blob/main/RFCs/002-Framework-Extensibility-Custom-Assertions.md)
+ - [Customize Running tests](https://github.com/Microsoft/testfx-docs/blob/main/RFCs/003-Customize-Running-Tests.md)
+ - [In-assembly parallel execution](https://github.com/Microsoft/testfx-docs/blob/main/RFCs/004-In-Assembly-Parallel-Execution.md)
+ - [Framework Extensibility for Custom Test Data Source](https://github.com/Microsoft/testfx-docs/blob/main/RFCs/005-Framework-Extensibility-Custom-DataSource.md)
+ - [DynamicData Attribute for Data Driven Tests](https://github.com/Microsoft/testfx-docs/blob/main/RFCs/006-DynamicData-Attribute.md)
+ - [DataSource Attribute Vs ITestDataSource](https://github.com/Microsoft/testfx-docs/blob/main/RFCs/007-DataSource-Attribute-VS-ITestDataSource.md)
+ - [Test case timeout via runsettings](https://github.com/Microsoft/testfx-docs/blob/main/RFCs/008-TestCase-Timeout.md)
+ - [Deltas from MSTest V1](https://github.com/Microsoft/testfx-docs/blob/main/docs/deltaWithMSTestV1.md)
+ - [Release Roadmap](https://github.com/Microsoft/testfx-docs/blob/main/docs/releases.md)
 
 ### Contributing
 There are many ways to contribute to VSTest

diff --git a/RFCs/004-In-Assembly-Parallel-Execution.md b/RFCs/004-In-Assembly-Parallel-Execution.md
@@ -69,8 +69,8 @@ Test lifecyle method semantics
 ## Conditioning in-assembly parallel execution - composition rules
 In-assembly parallel execution can be conditioned using the following means:
 1. as annotations in source code (as described in this document).
-2. as configuration properties set via a .runsettings file [[see here for more]](https://github.com/Microsoft/vstest-docs/blob/master/docs/configure.md).
-3. by passing runsettings arguments via the command line [[see here for more]](https://github.com/Microsoft/vstest-docs/blob/master/docs/RunSettingsArguments.md).
+2. as configuration properties set via a .runsettings file [[see here for more]](https://github.com/Microsoft/vstest-docs/blob/main/docs/configure.md).
+3. by passing runsettings arguments via the command line [[see here for more]](https://github.com/Microsoft/vstest-docs/blob/main/docs/RunSettingsArguments.md).
 
 (3) overrides (2) which in turn overrides (1). The ```[DoNotParallelize]``` annotation may be applied only to source code, and hence remains unaffected by these rules - thus, even if in-assembly parallel execution in conditioned via (2) or (3), specific program elements can still opt-out safely.
 

diff --git a/docs/contribute.md b/docs/contribute.md
@@ -133,9 +133,9 @@ Documentation for nuget.exe command line reference is [here](https://docs.micros
 The first level of diagnosis for adapter failures can start with enabling verbose logging in the Visual studio Test Platform itself. Here is how to turn that on:
 
 * **TP V1** : [This](https://blogs.msdn.microsoft.com/aseemb/2012/03/01/how-to-enable-ute-logs/) blog helps detail setting up diagnostic logging.
-* **TP V2**(The open-source cross-plat Test Platform): [This](https://github.com/Microsoft/vstest-docs/blob/master/docs/diagnose.md#collect-traces-using-command-line) section helps detail the process to enable diagnostic logging.
+* **TP V2**(The open-source cross-plat Test Platform): [This](https://github.com/Microsoft/vstest-docs/blob/main/docs/diagnose.md#collect-traces-using-command-line) section helps detail the process to enable diagnostic logging.
 
 One can always add a `Debugger.Launch` at the main entry points:
-* [MSTestDiscoverer.DiscoverTests](https://github.com/Microsoft/testfx/blob/master/src/Adapter/MSTest.CoreAdapter/MSTestDiscoverer.cs) for discovery.
-* [MSTestExecutor.RunTests](https://github.com/Microsoft/testfx/blob/master/src/Adapter/MSTest.CoreAdapter/MSTestExecutor.cs) - both the overloads that take sources and tests for execution.
+* [MSTestDiscoverer.DiscoverTests](https://github.com/Microsoft/testfx/blob/main/src/Adapter/MSTest.CoreAdapter/MSTestDiscoverer.cs) for discovery.
+* [MSTestExecutor.RunTests](https://github.com/Microsoft/testfx/blob/main/src/Adapter/MSTest.CoreAdapter/MSTestExecutor.cs) - both the overloads that take sources and tests for execution.
  Select the appropriate debugger and step through the code.
diff --git a/issuetracking.md b/issuetracking.md
@@ -1,13 +1,13 @@
 # Issue tracking
-The testfx project tracks issues and feature requests using the [issue template](https://github.com/Microsoft/testfx/blob/master/.github/ISSUE_TEMPLATE.md) for the testfx repository.
+The testfx project tracks issues and feature requests using the [issue template](https://github.com/Microsoft/testfx/blob/main/.github/ISSUE_TEMPLATE.md) for the testfx repository.
 
 ## Submitting an Issue
 First, please do a search in [issues](https://github.com/Microsoft/testfx/issues) to see if the issue or feature request has already been filed. Use this [query](https://github.com/Microsoft/testfx/issues?q=is%3Aopen+is%3Aissue+sort%3Areactions-%2B1-desc) to search for the most popular feature requests.
 If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment.
 - 👍 - upvote
 - 👎 - downvote
 
-If you cannot find an existing issue that describes your issue, submit it using the [issue template](https://github.com/Microsoft/testfx/blob/master/.github/ISSUE_TEMPLATE.md). Remember to follow the instruction mentioned therein carefully.
+If you cannot find an existing issue that describes your issue, submit it using the [issue template](https://github.com/Microsoft/testfx/blob/main/.github/ISSUE_TEMPLATE.md). Remember to follow the instruction mentioned therein carefully.
 
 ## Issue triage
 Please follow the guidelines in the issue template when filing an issue or a pull request.