Switch from master to main (Fixes #1595)

Signed-off-by: Alexander Brandes <mc.cache@web.de>

.github/workflows/codeql-analysis.yml

@@ -13,10 +13,10 @@ name: "CodeQL"
 
 on:
   push:
-    branches: [ master ]
+    branches: [ main ]
   pull_request:
     # The branches below must be a subset of the branches above
-    branches: [ master ]
+    branches: [ main ]
   schedule:
     - cron: '18 14 * * 2'
 

.github/workflows/release-drafter.yml

@@ -3,7 +3,7 @@ name: Release Drafter
 on:
   push:
     branches:
-      - master
+      - main
 
 jobs:
   update_release_draft:

CONTRIBUTING.md

@@ -20,8 +20,8 @@ included in the project:
 2. If you cloned a while ago, get the latest changes from upstream:
 
    ```bash
-   git checkout master
-   git pull upstream master
+   git checkout main
+   git pull upstream main
    ```
 
 3. Create a new topic branch (off the main project development branch) to
@@ -43,7 +43,7 @@ included in the project:
 6. Locally merge (or rebase) the upstream development branch into your topic branch:
 
    ```bash
-   git pull [--rebase] upstream master
+   git pull [--rebase] upstream main
    ```
 
 7. Push your topic branch up to your fork:
@@ -53,7 +53,7 @@ included in the project:
    ```
 
 8. [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
-   with a clear title and description against the `master` branch.
+   with a clear title and description against the `main` branch.
 
 **IMPORTANT**: By submitting a patch, you agree to allow the project owners to
 license your work under the terms of the [MIT License](LICENSE).

plugins/plugin-site/gatsby-config.mjs

@@ -53,7 +53,7 @@ config.plugins = [
         resolve: '@jenkinsci/gatsby-plugin-jenkins-layout',
         options: {
             siteUrl: 'https://plugins.jenkins.io/',
-            githubBranch: 'master',
+            githubBranch: 'main',
             githubRepo: 'jenkins-infra/plugin-site',
             reportAProblemTemplate: '4-bug.yml',
             theme: 'auto',