登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
登录
注册
代码拉取完成，页面将自动刷新
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
8
Star
0
Fork
3
src-anolis-os
/
zsh
代码
Issues
0
Pull Requests
1
Wiki
统计
流水线
服务
JavaDoc
PHPDoc
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
我知道了，不再自动展开
13
Auto Update from Upstream
开启的
文子方:a23
src-anolis-os:a23
文子方
创建于 2025-09-29 12:40
克隆/下载
HTTPS
SSH
复制
下载 Email Patch
下载 Diff 文件
Automatically synchronized with the latest code from upstream. ### RELAI - 自动同步时间：2025-09-29 12:40:03 - 上游仓库：src-anolis-os/zsh - 来源分支：wenyuzifang/zsh:a23 - 同步工具版本：auto-sync-bot/1.0.0 ### 关键日志内容: 2025-09-29 12:28:02,090 - INFO - project log file path: /home/lzx/workspace/001test/Upstream-Sync-workflow/cache/zsh-20250929122802.log 2025-09-29 12:28:02,090 - INFO - work_dir: /tmp/upstream_sync_2k_s16xj 2025-09-29 12:28:02,090 - INFO - starting sync from https://kojihub.stream.centos.org/kojifiles/vol/koji02/packages/zsh/5.9/15.el10/src/zsh-5.9-15.el10.src.rpm... 2025-09-29 12:28:02,090 - INFO - Gitee API 已初始化 2025-09-29 12:28:02,090 - INFO - Fork Manager 初始化成功: src-anolis-os/zsh 2025-09-29 12:28:02,090 - INFO - Pull Request Creator 已初始化 2025-09-29 12:28:02,090 - INFO - Gitee API 已初始化 2025-09-29 12:28:02,090 - INFO - Fork Manager 初始化成功: src-anolis-os/zsh 2025-09-29 12:28:02,091 - INFO - Pull Request Creator 已初始化 2025-09-29 12:28:02,128 - INFO - 确保fork存在，尝试第 1 次 2025-09-29 12:28:02,128 - INFO - Checking if repo has been forked by fork_owner 2025-09-29 12:28:02,667 - INFO - 开始 Fork 上游仓库：src-anolis-os/zsh 2025-09-29 12:28:02,667 - INFO - 开始 Fork：src-anolis-os/zsh 2025-09-29 12:28:03,792 - INFO - Fork 成功！ 2025-09-29 12:28:04,115 - INFO - Fork 仍在进行中，仓库信息不完整... 2025-09-29 12:28:09,498 - INFO - Fork 仓库 wenyuzifang/zsh 已准备就绪 2025-09-29 12:28:09,499 - INFO - Fork 成功 2025-09-29 12:28:09,803 - INFO - Fork 验证通过，可以继续操作 2025-09-29 12:28:09,804 - INFO - 准备克隆仓库，URL: https://gitee.com/wenyuzifang/zsh.git 2025-09-29 12:28:09,804 - INFO - 尝试克隆仓库，第 1 次 2025-09-29 12:28:10,160 - INFO - 仓库 https://gitee.com/wenyuzifang/zsh.git 可访问 2025-09-29 12:28:10,162 - INFO - 正在本地克隆仓库 → https://gitee.com/wenyuzifang/zsh.git 2025-09-29 12:28:13,682 - INFO - 本地克隆完成 → https://gitee.com/wenyuzifang/zsh.git 2025-09-29 12:28:13,682 - INFO - 仓库克隆成功 2025-09-29 12:28:13,682 - INFO - 开始更新上游代码（分支：a23） 2025-09-29 12:28:13,682 - INFO - 开始更新上游代码upstream_url：https://gitee.com/wenyuzifang/zsh.git 2025-09-29 12:28:13,689 - INFO - 已添加远程使用 token 认证 2025-09-29 12:28:14,108 - INFO - 安装 git 和 rpm-build 工具... 2025-09-29 12:28:32,316 - INFO - 解压 SRPM 包... 2025-09-29 12:28:53,409 - INFO - gitee仓库有patch 2025-09-29 12:28:53,409 - INFO - upstream仓库有patch 2025-09-29 12:28:54,973 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:29:21,862 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:29:48,419 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:30:11,663 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:30:15,323 - INFO - 2025-09-29 12:30:15,590 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:30:53,942 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:31:10,763 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:31:15,153 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:31:27,339 - INFO - 2025-09-29 12:31:27,614 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:32:02,244 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:32:12,410 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:32:17,563 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:32:36,100 - INFO - 2025-09-29 12:32:36,369 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:33:13,395 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:33:26,022 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:33:29,882 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:33:42,380 - INFO - 2025-09-29 12:33:42,731 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:34:12,048 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:34:19,481 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:34:24,393 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:34:38,655 - INFO - 2025-09-29 12:34:39,841 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:35:20,038 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:35:49,092 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:36:05,449 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:36:12,003 - INFO - 2025-09-29 12:36:12,239 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:36:44,726 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:37:00,857 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:37:07,503 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:37:24,715 - INFO - [{'Question': "Could you use one of the following word————BUGFIX, FEATURE————to describe this patch's purpose?", 'Scratchpad': 'Step 1: Examine the patch metadata.\n- The subject line says: \'[PATCH] 50658 + test: Enable to switch between C/UTF-8 locales in PCRE\'.\n- This indicates a functional improvement related to locale handling in PCRE regex support.\n- The inclusion of \'test\' suggests verification of behavior is added.\n\nStep 2: Analyze code changes in `pcre.c`.\n- The function `zpcre_utf8_enabled()` previously cached whether UTF-8 mode was enabled based on the initial locale.\n- A comment warned: \'value can toggle based on MULTIBYTE, so don\'t be too eager with caching\', but the old code did not respect this.\n- After the change, the return value depends on both:\n a) Whether PCRE has UTF-8 support (`have_utf8_pcre == 1`)\n b) Whether the current locale is UTF-8 (`!strcmp(nl_langinfo(CODESET), "UTF-8")`)\n- This means the decision is no longer cached statically — it dynamically respects locale changes.\n- Without this fix, switching `LANG=C` then back would lead to inconsistent or incorrect pattern matching.\n\nStep 3: Analyze test addition in `V07pcre.ztst`.\n- The test explicitly switches `LANG`, matches patterns involving multibyte character `é`, and expects success (exit code 0) in all cases.\n- In UTF-8 locale: `é` should match `^.$` (one character).\n- In `C` locale: `é` is two bytes, so should match `^..$` (two characters).\n- Then restore and match again as one character.\n- All pass only if PCRE correctly adapts to locale changes.\n\nStep 4: Determine if this is a BUGFIX or FEATURE.\n- A bug exists when locale switching leads to incorrect regex behavior due to stale caching.\n- The original code could return incorrect results after `LANG` changes because it relied on early caching without re-checking the locale.\n- The fact that there’s a warning comment about not being \'too eager with caching\' implies the original behavior was already known to be flawed.\n- The patch fixes that incorrect caching logic.\n- Furthermore, real user impact (e.g., segmentation fault reference in ztst file — \'workers/38307\') suggests stability/correctness issues.\n- Therefore, although new test coverage is added, the core change corrects faulty behavior rather than introducing new capability.\n\nJudgment: This is a BUGFIX because it resolves incorrect runtime behavior in locale-sensitive PCRE handling that could lead to mismatched patterns or inconsistent script behavior.', 'References': 'Patch subject line: \'Enable to switch between C/UTF-8 locales in PCRE\';\nCode comment in pcre.c: \'/* value can toggle based on MULTIBYTE, so don\\\'t be too eager with caching */\';\nChange in logic: moving `!strcmp(nl_langinfo(CODESET), "UTF-8")` into the return condition;\nTest case in V07pcre.ztst verifying correct behavior across `LANG=C` and UTF-8 transitions;\nExpected outputs all being 0, indicating successful matches only possible with correct dynamic evaluation.', 'Answer': 'BUGFIX'}, {'Question': "Could you describe what's good to apply this patch in less than 25 words, imperatively?", 'Scratchpad': 'The patch fixes incorrect caching of UTF-8 detection in PCRE by making it recheck the current locale on each call, allowing proper behavior when switching between C and UTF-8 locales. The test confirms correct matching in both modes. This is a bugfix because it corrects flawed logic that caused stale locale decisions.\n\nReference: Patch changes `zpcre_utf8_enabled()` to include `!strcmp(nl_langinfo(CODESET), "UTF-8")` in return condition, ensuring runtime check.\n\nReference: Test case verifies matching behavior across locale switches, which would fail if cache were stale.', 'References': "Patch subject: 'Enable to switch between C/UTF-8 locales in PCRE'; Code change in `pcre.c`: new return condition with `nl_langinfo(CODESET)`; Added test in `V07pcre.ztst` verifying multi-locale correctness.", 'Answer': 'Fix locale-sensitive PCRE behavior by dynamically checking UTF-8 mode instead of relying on stale cache.'}, {'Question': 'Does this patch relate to some specific architecture or simply generic code update using one of the following word————i386, x86_64, arm64, arm32, riscv32, riscv64, sw_64, loongarch64, powerpc, s390, alpha, mips, hpp, sparc, generic?', 'Scratchpad': 'Step 1: Examine the patch content for architecture-specific code.\n- The changes are in `Src/Modules/pcre.c` and `Test/V07pcre.ztst`.\n- `pcre.c` deals with PCRE (Perl Compatible Regular Expressions) integration in zsh, specifically locale-dependent UTF-8 handling.\n- No assembly code, compiler intrinsics, or conditional compilation for CPU architectures (like __x86_64__, __aarch64__, etc.) is present.\n\nStep 2: Check preprocessor directives.\n- The conditionals used are: `#if defined(MULTIBYTE_SUPPORT) && defined(HAVE_NL_LANGINFO) && defined(CODESET)`\n- These relate to feature availability (multibyte support, locale functions), not hardware architecture.\n\nStep 3: Analyze functionality.\n- The patch modifies logic for detecting UTF-8 locale at runtime using `nl_langinfo(CODESET)` and PCRE configuration.\n- This is purely about string and locale processing, independent of CPU instruction set or endianness.\n\nStep 4: Consider test file.\n- The test in `V07pcre.ztst` checks regex behavior under different `LANG` settings.\n- It uses standard shell syntax and does not invoke any architecture-specific behavior.\n\nConclusion: The patch applies universally across all platforms where zsh runs, regardless of underlying CPU. It is a portable, platform-agnostic fix related to internationalization and regular expression handling.', 'References': 'Patch modifies `Src/Modules/pcre.c` and `Test/V07pcre.ztst`; uses `nl_langinfo(CODESET)` and `pcre_config()`; no architecture-specific macros or code; functionality depends only on locale and PCRE support, not CPU type.', 'Answer': 'generic'}] 2025-09-29 12:37:24,716 - INFO - 版本一致，新增补丁，正在生成 changelog... 2025-09-29 12:37:24,716 - INFO - for patch: 0007-zsh-configure-c99.patch 2025-09-29 12:37:25,014 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:37:35,114 - INFO - Running agent with question: 2025-09-29 12:37:35,573 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:37:38,141 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:37:40,914 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:37:42,709 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:37:45,235 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:37:46,884 - INFO - Agent Raw Output: 2025-09-29 12:37:46,885 - INFO - LLM 原始输出: 2025-09-29 12:37:46,885 - INFO - for patch: 0003-zsh-fix-module-loading-problem-with-full-RELRO.patch 2025-09-29 12:37:47,186 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:01,659 - INFO - Running agent with question: 2025-09-29 12:38:02,120 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:07,106 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:09,096 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:11,424 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:13,414 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:15,515 - INFO - Agent Raw Output: 2025-09-29 12:38:15,515 - INFO - LLM 原始输出: 2025-09-29 12:38:15,515 - INFO - for patch: 0006-zsh-support-texinfo-7.0.patch 2025-09-29 12:38:15,820 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:29,334 - INFO - Running agent with question: 2025-09-29 12:38:29,744 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:33,652 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:37,169 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:38,356 - INFO - Agent Raw Output: 2025-09-29 12:38:38,356 - INFO - LLM 原始输出: 2025-09-29 12:38:38,357 - INFO - for patch: 0008-zsh-deletefilelist-segfault.patch 2025-09-29 12:38:38,620 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:52,711 - INFO - Running agent with question: 2025-09-29 12:38:53,095 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:55,603 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:38:57,386 - INFO - Agent Raw Output: 2025-09-29 12:38:57,386 - INFO - LLM 原始输出: 2025-09-29 12:38:57,386 - INFO - for patch: 0002-zsh-Use-int-main-in-test-c-codes.patch 2025-09-29 12:38:58,543 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:39:16,185 - INFO - Running agent with question: 2025-09-29 12:39:17,614 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:39:19,914 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:39:23,616 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:39:26,573 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:39:28,553 - INFO - Agent Raw Output: 2025-09-29 12:39:28,553 - INFO - LLM 原始输出: 2025-09-29 12:39:28,553 - INFO - for patch: 0004-zsh-enable-PCRE-locale-switching.patch 2025-09-29 12:39:28,854 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:39:48,367 - INFO - Running agent with question: #if defined(MULTIBYTE_SUPPORT) && defined(HAVE_NL_LANGINFO) && defined(CODESET) 2025-09-29 12:39:48,903 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:39:51,681 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:39:54,530 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:39:55,713 - INFO - Agent Raw Output: 2025-09-29 12:39:55,713 - INFO - LLM 原始输出: 2025-09-29 12:39:57,067 - INFO - HTTP Request: POST https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions "HTTP/1.1 200 OK" 2025-09-29 12:40:01,360 - INFO - 已更新 Version: 5.9 → 5.9 2025-09-29 12:40:01,360 - INFO - 已更新 %define anolis_release: 2 → 3 2025-09-29 12:40:01,360 - INFO - 在 Patch1 后插入新补丁 2025-09-29 12:40:01,361 - INFO - 已将 changelog 插入并保存到仓库 2025-09-29 12:40:01,364 - INFO - 处理非tarball文件: dotzprofile 2025-09-29 12:40:01,364 - INFO - 处理非tarball文件: dotzshrc 2025-09-29 12:40:01,364 - INFO - 处理非tarball文件: zshenv.rhs 2025-09-29 12:40:01,365 - INFO - 处理非tarball文件: zshrc.rhs 2025-09-29 12:40:01,365 - INFO - 处理非tarball文件: zprofile.rhs 2025-09-29 12:40:01,365 - INFO - 处理非tarball文件: zlogout.rhs 2025-09-29 12:40:01,366 - INFO - 处理非tarball文件: zlogin.rhs 2025-09-29 12:40:01,371 - INFO - 正在提交代码更改 2025-09-29 12:40:01,401 - INFO - 本地提交成功：Update code from upstream 2025-09-29 12:40:01,401 - INFO - 正在推送到 Fork 的 origin 远程 2025-09-29 12:40:03,018 - INFO - 本地推送成功：origin/a23 2025-09-29 12:40:03,018 - INFO - 正在创建 PR → a23 to a23 2025-09-29 12:40:03,019 - INFO - 创建 PR：Auto Update from Upstream
此 Pull Request 需要通过一些审核项
类型
指派人员
状态
测试
小龙
已测试通过
已完成
(1/1人)
此 Pull Request 可以被系统自动合并
怎样手动合并此 Pull Request
git checkout a23
git pull https://gitee.com/wenyuzifang/zsh.git a23
git push origin a23
评论
2
提交
1
文件
7
检查
代码问题
0
批量操作
展开设置
折叠设置
审查
Code Owner
审查人员
gongwen2021
gongwen2021
happy_orange
happy_orange
geliwei
geliwei
casparant
casparant
ZhouWeitao
yunqi-zwt
jiangbo.jacob
jiangbojacob
forrest_ly
forrest_ly
Meredith
yueeranna
未设置
最少人数
0
测试
gongwen2021
gongwen2021
happy_orange
happy_orange
geliwei
geliwei
casparant
casparant
ZhouWeitao
yunqi-zwt
jiangbo.jacob
jiangbojacob
forrest_ly
forrest_ly
Meredith
yueeranna
小龙
anolis-bot-ci
未设置
最少人数
1
优先级
不指定
严重
主要
次要
不重要
标签
anolis_cla_pass
anolis_test_pass
关联 Issue
未关联
Pull Request 合并后将关闭上述关联 Issue
里程碑
未关联里程碑
合并选项
合并后删除提交分支
提交分支为默认分支，无法删除
合并后关闭提到的 Issue
接受 Pull Request 时使用扁平化（Squash）合并
勾选此选项后，将建议使用 Squash Merge 方式合并以精简提交历史记录
参与者
（2）
1
https://gitee.com/src-anolis-os/zsh.git
git@gitee.com:src-anolis-os/zsh.git
src-anolis-os
zsh
zsh
点此查找更多帮助
搜索帮助
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大，如何减小？
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release（发行版）
将 PHP 项目自动发布到 packagist.org
评论
仓库举报
回到顶部
登录提示
该操作需登录 Gitee 帐号，请先登录后再操作。
立即登录
没有帐号，去注册
