Release of new features (v.1.0.0)

.github/CODEOWNERS

@@ -0,0 +1,23 @@
+# This file defines code ownership for automatic review assignments
+
+# Default owners for everything in the repo
+* @lenni108 @sfdamm @ClaudiaDuenzinger
+
+# Specific service owners
+/api/ @lenni108 @sfdamm
+/client/ @lenni108
+/gateway/ @sfdamm
+/user-svc/ @ClaudiaDuenzinger
+/concept-svc/ @lenni108
+/genai-svc/ @sfdamm
+
+# Infrastructure and CI/CD
+/.github/workflows/ @sfdamm
+/helm/ai-event-concepter/ @sfdamm
+/helm/monitor/ @ClaudiaDuenzinger
+/infrastructure/ @lenni108
+/monitoring/ @ClaudiaDuenzinger
+
+# Documentation
+/docs/ @lenni108
+*.md @lenni108 @sfdamm @ClaudiaDuenzinger

.github/pull_request_template.md

@@ -0,0 +1,35 @@
+## Description
+
+<!-- Describe the changes introduced by this PR -->
+
+## Related Issues
+
+<!-- Link to any related issues here using #issue_number -->
+
+## Type of Change
+
+- [ ] 🚀 New Feature
+- [ ] 🐛 Bug Fix
+- [ ] 🔧 Refactoring
+- [ ] 📝 Documentation Update
+- [ ] 🧪 Test Changes
+- [ ] 🛠️ CI/CD Improvements
+
+## How Has This Been Tested?
+
+<!-- Describe the tests you've run to verify your changes -->
+
+## Checklist
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published
+
+## Screenshots (if applicable)
+
+<!-- Add screenshots here if UI changes were made -->

.github/workflows/README.md

@@ -0,0 +1,93 @@
+# CI/CD Pipeline Documentation
+
+## Overview
+
+This directory contains the GitHub Actions workflow files that make up our CI/CD pipeline. The pipeline is structured to ensure proper separation of concerns between Continuous Integration (building/testing) and Continuous Deployment (deploying to environments).
+
+## Workflow Files
+
+### 1. [`ci.yml`](./ci.yml)
+
+**Purpose**: Handles all Continuous Integration tasks including code generation, testing, and building Docker images.
+
+**Key Features**:
+- API validation and code generation
+- Running tests for all services
+- Building and pushing Docker images
+- Building API documentation
+
+**Triggered by**:
+- Push to `main` or `dev` branches
+- Pull requests to `main` or `dev`
+
+### 2. [`cd.yml`](./cd.yml)
+
+**Purpose**: Handles all Continuous Deployment tasks to staging and production environments.
+
+**Key Features**:
+- Proper dependency on CI workflow completion
+- Environment-specific deployments (staging for `dev` branch, production for `main` branch)
+- Kubernetes deployments with Helm
+- Deployment verification
+
+**Triggered by**:
+- Successful completion of the CI workflow on `main` or `dev` branches
+
+### 3. [`infrastructure.yml`](./infrastructure.yml)
+
+**Purpose**: Manages infrastructure deployments using Terraform and Ansible.
+
+**Key Features**:
+- Creates and updates AWS infrastructure
+- Configures server environments
+- Manages environment-specific deployments
+
+**Triggered by**:
+- Manual workflow dispatch
+- Changes to infrastructure files on `main` branch
+
+### 4. [`validate_pr.yml`](./validate_pr.yml)
+
+**Purpose**: Validates pull requests for code quality and potential issues.
+
+**Key Features**:
+- Linting and static analysis
+- Size checks for large PRs
+- API spec validation
+
+**Triggered by**:
+- Pull request creation or updates
+
+## Pipeline Flow
+
+1. **Code Changes**: Developer makes changes and creates a PR
+2. **PR Validation**: `validate_pr.yml` runs checks on the PR
+3. **CI Pipeline**: After merge/push, `ci.yml` builds and tests the code
+4. **CD Pipeline**: After successful CI, `cd.yml` deploys to the appropriate environment
+
+## Environment Configuration
+
+- **Staging**: Deployed from the `dev` branch
+- **Production**: Deployed from the `main` branch
+
+## Key Improvements
+
+1. **Separation of Concerns**: CI and CD are clearly separated
+2. **Workflow Dependencies**: CD only runs after successful CI completion
+3. **Race Condition Prevention**: No more issues with deployments starting before builds complete
+4. **Simplified Structure**: Easier to understand and maintain
+
+## Team Responsibilities
+
+- **CI/CD Pipeline**: @sfdamm
+- **Kubernetes Helm Charts**: @sfdamm (ai-event-concepter) and @ClaudiaDuenzinger (monitor)
+- **Infrastructure**: @lenni108
+- **Monitoring**: @ClaudiaDuenzinger
+
+## Best Practices
+
+1. Always use `needs:` to ensure proper job execution order
+2. Use GitHub Environments for deployment protection rules
+3. Include verification steps after deployments
+4. Keep related jobs in the same workflow file
+5. Use descriptive job and step names