.github/workflows/default-ci.yaml

@@ -1,4 +1,4 @@
-name: "Professional Services CI"
+name: "Default CI"
 
 on:
   push:

.github/workflows/github-mirror-ci.yaml

@@ -28,11 +28,11 @@ jobs:
       - name: Push to Public Repo
         run: |
           echo "Setting up remote..."
-          git config --global user.name "prof-service-sync-bot"
-          git config --global user.email "prof-service-sync-bot@digits.schwarz"
+          git config --global user.name "ps-sync-bot"
+          git config --global user.email "ps-sync-bot@digits.schwarz"
 
           # Add the GitHub remote using the SSH protocol
-          git remote add public git@github.com:stackitcloud/professional-services.git
+          git remote add public git@github.com:stackitcloud/stackit-ps-solutions.git
 
           echo "Pushing main branch to GitHub..."
           git push public main --force

GOVERNANCE.md

@@ -0,0 +1,41 @@
+# Project Governance: STACKIT PS Solutions
+
+This document defines the management, ownership, and maintenance processes for the STACKIT PS Solutions repository.
+
+## 1. Strategy & "The Story"
+
+This repository serves as a bridge between internal excellence and public visibility.
+
+- **Internal Git (Source of Truth):** The primary repository is hosted on our internal STACKIT Git instance. All internal communication, documentation, and chat links MUST point to the internal instance to promote our own infrastructure and tools.
+- **GitHub (Public Mirror):** The GitHub repository is a mirror intended for external visibility, SEO, and accessibility for AI models (LLMs). It helps customers find our solutions and establishes STACKIT as a thought leader in cloud automation.
+
+## 2. Ownership
+
+### 2.1 Organizational Ownership
+
+The repository is owned by the **STACKIT Professional Services** organization. High-level decisions regarding repository structure, licensing, and global policies are managed by the Core Maintainers team.
+
+### 2.2 Example & Module Ownership
+
+Individual examples or modules within the repository have specific owners, documented in their respective `MAINTAINERS.md` files.
+
+- **Responsibility:** Owners are responsible for the technical health, periodic updates (e.g., dependency bumps), and community feedback for their specific content.
+- **Handover:** If an owner leaves the project or company, ownership reverts to the Core Maintainers until a new owner is assigned.
+
+## 3. Review & Quality Assurance
+
+To ensure high standards and security, we follow a strict contribution process:
+
+- **4-Eyes Principle:** No code enters the `main` branch without at least one successful Peer Review.
+- **Automated Validation:** Every Pull Request must pass the CI pipeline, which includes:
+  - Linting and formatting checks.
+  - License header verification (Apache 2.0).
+  - Secret scanning (Trufflehog).
+- **Best Effort Policy:** While we strive for quality, the content is provided "as-is." Use in production environments requires independent validation by the user.
+
+## 4. Mirroring Process
+
+The synchronization between the internal Git and GitHub is fully automated:
+
+1.  Changes are merged into the internal `main` branch.
+2.  A GitHub Action triggers on every push to `main`.

README.md

@@ -1,6 +1,6 @@
-# STACKIT Professional Services
+# STACKIT PS Solutions
 
-Welcome to the central repository for STACKIT Professional Services examples, scripts, and boilerplate code!
+Welcome to the central repository for STACKIT examples, scripts, and boilerplate code!
 
 > **⚠️ REPOSITORY MIRROR NOTICE**
 >