Git工作流实践：从分支策略到CI/CD集成的团队协作方案

master         # 生产分支，只接受来自release的merge，且必须通过全部CI
release/       # 预发布分支，格式：release/v1.2.3，只做bug修复
develop        # 开发分支，日常集成点，所有feature/xxx合并到此
feature/       # 功能分支，格式：feature/【模块】-【JIRA编号】-【简述】，如feature/user-login-JIRA-123
hotfix/        # 紧急修复分支，格式：hotfix/【bug编号】-【简述】

master: 允许merge（需要approval），禁止push
develop: 允许merge，禁止push（可选，我们允许push但强制CI通过）
release/*: 允许merge，禁止push

# 在团队开发机上执行一次
git config --global push.recurseSubmodules check
git config --global alias.pf 'push --force-with-lease'  # 限制force push

## Review Checklist
- [ ] 代码风格符合lint规则（已通过ESLint/Prettier）
- [ ] 无死代码或注释掉的代码
- [ ] 单元测试覆盖率≥80%（新增代码）
- [ ] 不影响现有功能（已执行回归测试）
- [ ] 文档或注释已更新（如果必要）

# .gitlab-ci.yml 片段
review-rules:
  stage: review
  script:
    - |
      # 检查commit message格式：必须包含JIRA编号
      COMMITS=$(git log origin/$CI_MERGE_REQUEST_TARGET_BRANCH_NAME..HEAD --format="%s")
      while IFS= read -r line; do
        if ! echo "$line" | grep -qE '^(feat|fix|docs|refactor)\([^)]+\): \[JIRA-\d+\] .+'; then
          echo "❌ 不合规的commit: $line"
          echo "规范格式: feat|fix|docs|refactor(模块): [JIRA-123] 描述"
          exit 1
        fi
      done <<< "$COMMITS"
      echo "✅ 所有commit格式合规"
  only:
    - merge_requests

pipeline {
    agent any

    environment {
        NODE_VERSION = '16'
        JAVA_VERSION = '11'
        SONAR_TOKEN = credentials('sonar-token')
    }

    stages {
        stage('Checkout') {
            steps {
                checkout scm
                script {
                    // 获取当前分支名（Jenkins自动注入）
                    env.BRANCH_NAME = env.BRANCH_NAME ?: sh(script: 'git rev-parse --abbrev-ref HEAD', returnStdout: true).trim()
                }
            }
        }

        stage('Lint & Test') {
            steps {
                sh """
                    npm ci
                    npm run lint
                    npm run test:coverage
                """
            }
            post {
                failure {
                    // 发Slack通知，带上commit信息
                    slackSend(
                        channel: '#dev-ci',
                        color: 'danger',
                        message: "❌ ${env.BRANCH_NAME} Lint/Test失败: ${env.BUILD_URL}"
                    )
                }
            }
        }

        stage('Build') {
            when {
                // 只在master、release、feature分支构建
                expression { env.BRANCH_NAME ==~ /^(master|release\/.*|feature\/.*)$/ }
            }
            steps {
                sh 'npm run build:prod'
            }
        }

        stage('Deploy to Dev') {
            when {
                expression { env.BRANCH_NAME.startsWith('feature/') }
            }
            steps {
                sh "scp dist/* dev-server:/var/www/${env.BRANCH_NAME}/"
                echo "已部署到开发环境: http://dev.xxx.com/${env.BRANCH_NAME}"
            }
        }

        stage('Deploy to Staging') {
            when {
                expression { env.BRANCH_NAME.startsWith('release/') }
            }
            steps {
                sh 'ansible-playbook deploy-staging.yml -e version=${env.BRANCH_NAME#release/}'
            }
        }

        stage('Deploy to Production') {
            when {
                expression { env.BRANCH_NAME == 'master' }
            }
            input {
                message "确认部署到生产环境？"
                ok "确认部署"
            }
            steps {
                sh 'ansible-playbook deploy-prod.yml'
            }
        }
    }

    post {
        success {
            slackSend(
                channel: '#dev-ci',
                color: 'good',
                message: "✅ ${env.BRANCH_NAME} 构建成功，部署完成"
            )
        }
    }
}