Changed references to the master branch to main (#2848)

Author: dennisdoomen

.github/workflows/code_quality.yml

@@ -5,7 +5,7 @@ on:
   pull_request_target:
   push:
     branches:
-      - master
+      - main
       - develop
 
 jobs:
@@ -20,7 +20,7 @@ jobs:
       - name: 'Qodana Scan'
         uses: JetBrains/qodana-action@v2024.2
         with:
-          upload-result: ${{ github.ref_name == 'master' || github.ref_name == 'develop' }}
+          upload-result: ${{ github.ref_name == 'main' || github.ref_name == 'develop' }}
           args: --baseline,qodana.sarif.json,--ide,QDNET
           pr-mode: ${{ github.event_name == 'pull_request_target' }}
         env:

docs/.travis.yml

@@ -6,6 +6,6 @@ script:
 branches:
   only:
     # Change this to gh-pages if you're deploying using the gh-pages branch
-    - master
+    - main
 rvm:
  - 2.4

docs/_pages/about.md

@@ -59,7 +59,7 @@ Fluent Assertions supports the following unit test frameworks:
 
 As you may have noticed, the purpose of this open-source project is to not only be the best assertion framework in the .NET realm, but to also demonstrate high-quality code.
 We heavily practice Test Driven Development and one of the promises TDD makes is that unit tests can be treated as your API's documentation.
-So although you are free to go through the many examples here, please consider to analyze the many [unit tests](https://github.com/fluentassertions/fluentassertions/tree/master/Tests/FluentAssertions.Specs).
+So although you are free to go through the many examples here, please consider to analyze the many [unit tests](https://github.com/fluentassertions/fluentassertions/tree/main/Tests/FluentAssertions.Specs).
 
 ## Who is behind this project
 

docs/_pages/extensibility.md

@@ -96,7 +96,7 @@ So in this case, our nicely created `ContainFile` extension method will display
 
 ## Rendering objects with beauty
 
-Whenever Fluent Assertions raises an assertion exception, it will use value formatters to render a display representation of an object. Notice that these things are supposed to do more than just calling `Format`. A good formatter will include the relevant parts and hide the irrelevant parts. For instance, the `DateTimeOffsetValueFormatter` is there to give you a nice human-readable representation of a date and time with offset. It will only show the parts of that value that have non-default values. Check out the [specs](https://github.com/fluentassertions/fluentassertions/blob/master/Tests/FluentAssertions.Specs/Formatting/FormatterSpecs.cs) to see some examples of that.
+Whenever Fluent Assertions raises an assertion exception, it will use value formatters to render a display representation of an object. Notice that these things are supposed to do more than just calling `Format`. A good formatter will include the relevant parts and hide the irrelevant parts. For instance, the `DateTimeOffsetValueFormatter` is there to give you a nice human-readable representation of a date and time with offset. It will only show the parts of that value that have non-default values. Check out the [specs](https://github.com/fluentassertions/fluentassertions/blob/main/Tests/FluentAssertions.Specs/Formatting/FormatterSpecs.cs) to see some examples of that.
 
 You can hook-up your own formatters in several ways, for example by calling the static method `FluentAssertions.Formatting.Formatter.AddFormatter(IValueFormatter)`. But what does it mean to build your own? Well, a value formatter just needs to implement the two methods `IValueFormatter` declares. First, it needs to tell FA whether your formatter can handle a certain type by implementing the well-named method `CanHandle(object)`. The other one is there to, no surprises here, render it to a string.
 

docs/_pages/introduction.md

@@ -149,4 +149,4 @@ Expected string to be "Expected" with a length of 8, but "Actual" has a length o
     at........
 ```
 
-For more information take a look at the [AssertionScopeSpecs.cs](https://github.com/fluentassertions/fluentassertions/blob/master/Tests/FluentAssertions.Specs/Execution/AssertionScopeSpecs.cs) in Unit Tests.
+For more information take a look at the [AssertionScopeSpecs.cs](https://github.com/fluentassertions/fluentassertions/blob/main/Tests/FluentAssertions.Specs/Execution/AssertionScopeSpecs.cs) in Unit Tests.

docs/_pages/typesandmethods.md

@@ -125,4 +125,4 @@ AllTypes.From(assembly)
   .ThatAreNotInNamespace("Internal.Main.Test");
 ```
 
-There are so many possibilities and specialized methods that none of these examples do them good. Check out the [TypeAssertionSpecs](https://github.com/fluentassertions/fluentassertions/tree/master/Tests/FluentAssertions.Specs/Types) from the source for more examples.
+There are so many possibilities and specialized methods that none of these examples do them good. Check out the [TypeAssertionSpecs](https://github.com/fluentassertions/fluentassertions/tree/main/Tests/FluentAssertions.Specs/Types) from the source for more examples.

docs/staticman.yml

@@ -23,7 +23,7 @@ comments:
   #
   # Name of the branch being used. Must match the one sent in the URL of the
   # request.
-  branch: "master"
+  branch: "main"
 
   commitMessage: "New comment"