feat: ci/cd

Author: LeoPaulJulie

.commitlintrc.json

@@ -0,0 +1,41 @@
+{
+  "extends": ["@commitlint/config-conventional"],
+  "rules": {
+    "type-enum": [
+      2,
+      "always",
+      [
+        "feat",
+        "fix",
+        "docs",
+        "style",
+        "refactor",
+        "perf",
+        "test",
+        "build",
+        "ci",
+        "chore",
+        "revert"
+      ]
+    ],
+    "scope-enum": [
+      2,
+      "always",
+      [
+        "core",
+        "ui",
+        "auth",
+        "network",
+        "di",
+        "firebase",
+        "docs",
+        "config"
+      ]
+    ],
+    "subject-case": [2, "never", ["sentence-case", "start-case", "pascal-case", "upper-case"]],
+    "subject-empty": [2, "never"],
+    "subject-full-stop": [2, "never", "."],
+    "type-case": [2, "always", "lower-case"],
+    "type-empty": [2, "never"]
+  }
+}

.czrc

@@ -0,0 +1,59 @@
+{
+  "path": "cz-conventional-changelog",
+  "types": {
+    "feat": {
+      "description": "A new feature",
+      "title": "Features"
+    },
+    "fix": {
+      "description": "A bug fix",
+      "title": "Bug Fixes"
+    },
+    "docs": {
+      "description": "Documentation only changes",
+      "title": "Documentation"
+    },
+    "style": {
+      "description": "Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)",
+      "title": "Styles"
+    },
+    "refactor": {
+      "description": "A code change that neither fixes a bug nor adds a feature",
+      "title": "Code Refactoring"
+    },
+    "perf": {
+      "description": "A code change that improves performance",
+      "title": "Performance Improvements"
+    },
+    "test": {
+      "description": "Adding missing tests or correcting existing tests",
+      "title": "Tests"
+    },
+    "build": {
+      "description": "Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)",
+      "title": "Builds"
+    },
+    "ci": {
+      "description": "Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)",
+      "title": "Continuous Integrations"
+    },
+    "chore": {
+      "description": "Other changes that don't modify src or test files",
+      "title": "Chores"
+    },
+    "revert": {
+      "description": "Reverts a previous commit",
+      "title": "Reverts"
+    }
+  },
+  "scopes": [
+    "core",
+    "ui",
+    "auth",
+    "network",
+    "di",
+    "firebase",
+    "docs",
+    "config"
+  ]
+}

.editorconfig

@@ -0,0 +1,20 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.{dart,yaml,yml}]
+indent_size = 2
+
+[*.{md,markdown}]
+trim_trailing_whitespace = false
+
+[*.{sh,bash}]
+indent_size = 2
+
+[Makefile]
+indent_style = tab

.fvmrc

@@ -0,0 +1,3 @@
+{
+  "flutter": "3.35.2"
+}

.githooks/commit-msg

@@ -0,0 +1,41 @@
+#!/bin/bash
+
+# Conventional Commits validation hook
+# This hook validates commit messages against conventional commits format
+
+commit_regex='^(feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert)(\(.+\))?: .{1,50}'
+
+error_msg="❌ Invalid commit message format!
+
+Your commit message should follow the Conventional Commits specification:
+<type>[optional scope]: <description>
+
+Types:
+  feat:     A new feature
+  fix:      A bug fix
+  docs:     Documentation only changes
+  style:    Changes that do not affect the meaning of the code
+  refactor: A code change that neither fixes a bug nor adds a feature
+  perf:     A code change that improves performance
+  test:     Adding missing tests or correcting existing tests
+  build:    Changes that affect the build system or external dependencies
+  ci:       Changes to our CI configuration files and scripts
+  chore:    Other changes that don't modify src or test files
+  revert:   Reverts a previous commit
+
+Examples:
+  ✅ feat: add user authentication
+  ✅ fix(auth): resolve login validation issue
+  ✅ docs: update README with installation steps
+  ✅ refactor(api): simplify user service logic
+
+Your commit message: $(cat $1)
+"
+
+if ! grep -qE "$commit_regex" "$1"; then
+    echo "$error_msg"
+    exit 1
+fi
+
+echo "✅ Commit message format is valid!"
+exit 0

.github/SECRETS.md

@@ -0,0 +1,110 @@
+# GitHub Secrets Configuration
+
+This document describes the required secrets for the CI/CD pipeline.
+
+## Required Secrets
+
+Configure these secrets in your GitHub repository settings (`Settings > Secrets and variables > Actions`):
+
+### pub.dev Configuration
+- **`PUB_CREDENTIALS`** - Complete credentials JSON file for pub.dev publishing (includes refresh token for auto-renewal)
+
+### Optional Notification Secrets
+- **`SLACK_WEBHOOK_URL`** - Webhook URL for Slack notifications (optional)
+- **`DISCORD_WEBHOOK_URL`** - Webhook URL for Discord notifications (optional)
+
+## Setting Up Secrets
+
+### 1. pub.dev Setup
+
+1. **Generate pub.dev token:**
+   ```bash
+   # Login to pub.dev locally first
+   dart pub login
+   
+   # Get your credentials file
+   cat ~/.pub-cache/credentials.json
+   ```
+
+2. **Copy complete credentials:**
+   - Copy the ENTIRE JSON content from the credentials.json file
+   - Include the `refreshToken` for automatic token renewal
+   - This is your `PUB_CREDENTIALS` value
+
+3. **Add to GitHub:**
+   - Go to repository Settings > Secrets and variables > Actions
+   - Click "New repository secret"
+   - Name: `PUB_CREDENTIALS`
+   - Value: The complete JSON from step 2
+
+### 2. Notification Setup (Optional)
+
+#### Slack
+```bash
+# Create a Slack webhook in your workspace
+# Add the webhook URL as SLACK_WEBHOOK_URL secret
+```
+
+#### Discord
+```bash
+# Create a Discord webhook in your server
+# Add the webhook URL as DISCORD_WEBHOOK_URL secret
+```
+
+## Security Best Practices
+
+- Use tokens with minimal required permissions
+- Rotate tokens regularly
+- Never log secret values in workflows
+- Use environment-specific secrets when possible
+
+## Verification
+
+Test your setup:
+```bash
+# Dry run to test authentication
+melos publish --dry-run
+```
+
+## Troubleshooting
+
+### Common Issues
+
+#### pub.dev Authentication Failed
+```
+Error: 401 Unauthorized when accessing https://pub.dartlang.org
+```
+**Solution:** Check that `PUB_CREDENTIALS` contains valid JSON with both accessToken and refreshToken.
+
+#### Token Expired
+```
+Error: Token has expired
+```
+**Solution:** Generate a new token using `dart pub login` and update the secret.
+
+#### Missing Permissions
+```
+Error: Insufficient permissions to publish package
+```
+**Solution:** Ensure you have publisher permissions for the package on pub.dev.
+
+## Token Management
+
+### Rotating Tokens
+1. Generate new token: `dart pub login`
+2. Update GitHub secret with new token
+3. Test with dry-run: `melos publish --dry-run`
+
+### Monitoring
+- Monitor pub.dev package dashboard
+- Set up alerts for failed releases
+- Review workflow logs regularly
+
+## Package Publishing Process
+
+1. **Authentication**: GitHub Actions uses `PUB_TOKEN` to authenticate
+2. **Validation**: Packages are validated before publishing
+3. **Publishing**: Only changed packages are published
+4. **Verification**: Success/failure is reported in workflow logs
+
+For more details, see the main [CI/CD documentation](../docs/CI-CD.md).