git-recursive脚本同步git仓库时，工作不正常
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 495
- Forks
- 178
- PR merge metrics
- No merged PRs in 30d
Description
配置：
#/etc/tunasync/mirrors.conf.d/boost.conf
[[mirrors]]
name = "boost.git"
provider = "command"
command = "/home/tunasync-scripts/git-recursive.sh"
upstream = "https://github.com/boostorg/boost.git"
docker_image = "tunathu/tunasync-scripts:latest"
size_pattern = "size-pack: ([0-9\\.]+[KMGTP])"
[mirrors.env]
MIRROR_BASE_URL="http://mirror.example.com/"
WORKING_DIR_BASE="/srv/git-mirror/"
GENERATED_SCRIPT="/srv/git-mirror/boost-git.sh"
RECURSIVE="1"
worker日志提示该镜像任务Success，但查看内容时发现，实际只同步了url中指定的仓库。而里面submodules的其他仓库没有被正确执行同步。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the configured entry point, git-recursive.sh, and reproduce the Boost mirror job using the shown environment variables. Compare the worker's successful status with the submodule repositories listed by the upstream repository, using the linked log for details. Done means the top-level repository and its submodules are synchronized correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100