chore: rename default branch from master to main

Update all workflow triggers, checkout refs, documentation, mkdocs
config, and release docs to reference 'main' instead of 'master'.

Includes-AI-Code: true
Made-with: Cursor

Author: ZgjimHaziri

.github/workflows/build-or-publish.yml

@@ -3,7 +3,7 @@ name: Build / Publish Workflow
 on:
   push:
     branches:
-      - 'master'
+      - 'main'
       - 'release/*'
     paths-ignore:
       - '.github/**'
@@ -62,7 +62,7 @@ jobs:
     name: Create release branch (CalVer) and Publish
     runs-on: ubuntu-latest
     needs: detect-bump
-    if: needs.detect-bump.outputs.is_bump == 'true' && github.ref == 'refs/heads/master'
+    if: needs.detect-bump.outputs.is_bump == 'true' && github.ref == 'refs/heads/main'
     permissions:
       id-token: write
       contents: write
@@ -90,7 +90,7 @@ jobs:
           echo "release_branch=${release_branch}" >> $GITHUB_OUTPUT
           echo "Selected release branch: ${release_branch}"
 
-      - name: Create and push release branch from current master commit
+      - name: Create and push release branch from current main commit
         env:
           GIT_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |

.github/workflows/build.yml

@@ -2,7 +2,7 @@ name: Build Pull Request
 
 on:
   pull_request:
-    branches: [ master ]
+    branches: [ main ]
 jobs:
   build:
     runs-on: ubuntu-latest

.github/workflows/create-release.yml

@@ -37,9 +37,9 @@ jobs:
           echo "Validating base branch: $BASE"
           echo "Requested bump type: $BUMP"
 
-          # Restrict workflow execution to master or release/*
-          if [[ ! "$BASE" =~ ^master$ ]] && [[ ! "$BASE" =~ ^release\/.+$ ]]; then
-            echo "ERROR: workflow may only be dispatched from 'master' or a 'release/*' branch. Selected: $BASE"
+          # Restrict workflow execution to main or release/*
+          if [[ ! "$BASE" =~ ^main$ ]] && [[ ! "$BASE" =~ ^release\/.+$ ]]; then
+            echo "ERROR: workflow may only be dispatched from 'main' or a 'release/*' branch. Selected: $BASE"
             exit 1
           fi
 

.github/workflows/sonarcloud-scan.yml

@@ -4,7 +4,7 @@ on:
   pull_request:
   push:
     branches:
-      - master
+      - main
 
 jobs:
   build:

README.md

@@ -73,7 +73,7 @@ content-cli push package -p my-dev-profile --spaceKey my-cool-space -f interesti
 ```
 
 A comprehensive list of Content CLI capabilities can be found in the 
-[documentation](https://github.com/celonis/content-cli/tree/master/docs).
+[documentation](https://github.com/celonis/content-cli/tree/main/docs).
 
 You can still explore the full capabilities of Content CLI and the list of options for the different commands 
 by using the `-h` option in your command.
@@ -159,14 +159,14 @@ npm i -g @celonis/content-cli
 ## Contributing
 
 We encourage public contributions! Please check 
-[CONTRIBUTING.md](https://github.com/celonis/content-cli/blob/master/CONTRIBUTING.md) for details on our 
+[CONTRIBUTING.md](https://github.com/celonis/content-cli/blob/main/CONTRIBUTING.md) for details on our 
 code of conduct.
 
-For details on command development, refer to the [How to Add a Command](https://github.com/celonis/content-cli/blob/master/docs/how-to-add-command.md) guide.
+For details on command development, refer to the [How to Add a Command](https://github.com/celonis/content-cli/blob/main/docs/how-to-add-command.md) guide.
 
 ## License
 
 Copyright (c) 2021 Celonis SE
 
 This project is licensed under the MIT License - 
-see [LICENSE](https://github.com/celonis/content-cli/blob/master/LICENSE) file for details.
+see [LICENSE](https://github.com/celonis/content-cli/blob/main/LICENSE) file for details.

docs/how-to-add-command.md

@@ -159,4 +159,4 @@ You are free to adapt the structure based on complexity.
 
 ## Useful Examples
 
-Example group: [configuration-management](https://github.com/celonis/content-cli/tree/master/src/commands/configuration-management)
+Example group: [configuration-management](https://github.com/celonis/content-cli/tree/main/src/commands/configuration-management)

docs/how-to-release.md

@@ -10,7 +10,7 @@ The Content CLI uses a **trunk-based workflow** with **semantic version bumps**
 
 | **Branch Type** | **Purpose**                                                                        |
 |------------------|------------------------------------------------------------------------------------|
-| `master` | Main development branch; represents the development environment.                   |
+| `main` | Main development branch; represents the development environment.                   |
 | `release/*` | Release branches named using CalVer format (e.g., `release/20251009-091337_RC00`). |
 
 Publishing happens **only** when a version bump PR is merged.
@@ -19,28 +19,28 @@ Publishing happens **only** when a version bump PR is merged.
 
 ## Developing a New Feature
 
-1. Create a feature branch from `master`.
+1. Create a feature branch from `main`.
 2. Implement and test your feature.
-    - Testing should be done locally. Check this guide for [testing your local build of master](https://github.com/celonis/content-cli/blob/master/README.md#building-and-using-the-project-locally).
-3. Open a PR targeting `master`.
-4. After approval, merge your PR into `master`.
-    - Merging to `master` **does not** publish anything — it only updates the development state of the CLI.
+    - Testing should be done locally. Check this guide for [testing your local build of main](https://github.com/celonis/content-cli/blob/main/README.md#building-and-using-the-project-locally).
+3. Open a PR targeting `main`.
+4. After approval, merge your PR into `main`.
+    - Merging to `main` **does not** publish anything — it only updates the development state of the CLI.
 
 ---
 
 ## Creating a Release
 
-When the `master` branch is stable and ready for deployment, use the **Create Release** workflow.
+When the `main` branch is stable and ready for deployment, use the **Create Release** workflow.
 
 ### Steps
 
 1. Go to **Actions → Create Release → Run workflow**.
 2. Choose the bump type (`patch`, `minor`, or `major`).
 3. The workflow will:
-    - Validate that it’s running from `master` or a `release/*` branch.
+    - Validate that it’s running from `main` or a `release/*` branch.
     - Create an automation branch (`automation/release-bump-<timestamp>`).
     - Bump the version and push a commit like `[Release] Bump version to x.x.x`.
-    - Open a **PR to the same branch** from which it was triggered (to master or release branch).
+    - Open a **PR to the same branch** from which it was triggered (to main or release branch).
 
 4. When the PR is approved and merged:
     - The **Build / Publish** workflow detects the version bump commit.
@@ -69,7 +69,7 @@ When a bug is discovered in an existing published version:
 
 | **Workflow** | **Trigger** | **Purpose** |
 |---------------|-------------|--------------|
-| **Build Pull Request** | On PR to `master` | Builds and tests changes before merging. |
+| **Build Pull Request** | On PR to `main` | Builds and tests changes before merging. |
 | **Create Release** | Manual trigger (`workflow_dispatch`) | Creates a PR with a version bump on the current branch. |
-| **Build / Publish** | On merge to `master` or `release/*` | Detects version bumps → builds, tags, and publishes. |
+| **Build / Publish** | On merge to `main` or `release/*` | Detects version bumps → builds, tags, and publishes. |
 

mkdocs.yaml

@@ -1,6 +1,6 @@
 site_name: Content CLI
 repo_url: https://github.com/celonis/content-cli
-edit_uri: edit/master/docs/
+edit_uri: edit/main/docs/
 docs_dir: ./docs
 
 plugins: