Files
document_analyzer/scripts/_common.sh
T
pzhang_zywl a8964db151
CI / test (pull_request) Successful in 18s
fix: 将 Gitea 配置迁移到 ~/.gitea/config.yaml 多账号配置体系
- 新增 _get_gitea_config.py 从 YAML 读取 URL/repo/token
- _common.sh 改为通过 eval python 脚本加载配置
- GITEA_CICD_SETUP.md / DEV_AGENT.md / QE_AGENT.md 更新文档
- CI 工作流改用 ${{ gitea.server_url }} / ${{ gitea.repository }}

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-06-05 17:17:48 +08:00

90 lines
3.8 KiB
Bash

#!/usr/bin/env bash
# _common.sh — shared functions for dev-agent / qe-agent startup scripts
# Source this file from start_dev_agent.sh or start_qe_agent.sh
set -eu
# ── Resolve paths ──────────────────────────────────────────────────────────────
_COMMON_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
PROJECT_DIR="${PROJECT_DIR:-$(cd "$_COMMON_DIR/.." && pwd)}"
# ── Load Gitea configuration ────────────────────────────────────────────────────
# Primary: ~/.gitea/config.yaml (requires GITEA_USER)
# Fallback: scripts/.env (backwards compat)
if ! eval "$(python "$_COMMON_DIR/_get_gitea_config.py" 2>/dev/null)"; then
# Fallback: source .env directly
if [ -f "$_COMMON_DIR/.env" ]; then
source "$_COMMON_DIR/.env"
fi
fi
# ── Validate required environment ──────────────────────────────────────────────
require_token() {
if [ -z "${GITEA_API_TOKEN:-}" ]; then
echo "ERROR: GITEA_API_TOKEN is not set." >&2
echo "Set it in ~/.gitea/config.yaml (with GITEA_USER) or scripts/.env." >&2
exit 1
fi
}
# ── Print banner ───────────────────────────────────────────────────────────────
banner() {
local role="${1:-Agent}"
echo "============================================"
echo " ${role}-Agent 启动器"
echo "============================================"
echo ""
}
# ── Launch agent in selected mode ──────────────────────────────────────────────
# Usage: launch_agent <agent-file> <agent-name> <single-shot-task> <polling-instruction>
#
# agent-name is the persona name (e.g. "Dev-Agent", "QE-Agent"). It is used to
# prefix prompts so the model adopts the correct identity.
#
# Mode 1 (single-shot): claude -p, runs once and exits.
# --dangerously-skip-permissions avoids blocking in non-interactive mode.
# The project .claude/settings.json already sets permissionMode: bypass.
#
# Mode 2 (interactive polling): claude --agent, opens Claude Code TUI.
# The agent file defines startup behavior (e.g. /loop 10m) and the
# user can observe or interact at any time.
launch_agent() {
local agent_file="$1"
local agent_name="$2"
local single_shot_task="$3"
local polling_instruction="${4:-}"
echo "模式选择:"
echo " [1] 单次任务 — 检查 Issue 并处理,完成后自动退出 (automode)"
echo " [2] 互动轮询 — 进入 Claude Code 界面,每 10 分钟自动轮询"
echo ""
read -r -p "请输入 (1/2): " mode
echo ""
case "$mode" in
1)
echo "执行单次检查 (automode)..."
echo ""
cd "$PROJECT_DIR"
claude -p \
--agent "$agent_file" \
--dangerously-skip-permissions \
"你是 ${agent_name}${single_shot_task}"
;;
2)
echo "启动互动轮询模式..."
echo "${agent_name} 进入 Claude Code 界面后将自动开始轮询"
echo "你可以随时输入指令与 Agent 互动,按 Ctrl+C 停止"
echo ""
cd "$PROJECT_DIR"
claude --agent "$agent_file" \
"你是 ${agent_name}${polling_instruction}"
;;
*)
echo "无效选择,请输入 1 或 2。"
exit 1
;;
esac
}