89c1b3c2创建于 4月15日历史提交

文件	最后提交记录	最后更新时间
images	Added documentation for Importing an External Workflow Co-authored-by: michaelhuawei<michael.atamuk@huawei.com> Co-authored-by: Nikita Merkulov<nikita.merkulov1@huawei.com> # message auto-generated for no-merge-commit merge: !982 merge doc-import-workflow into develop Added documentation for Importing an External Workflow Created-by: nikita-mee Commit-by: nikita-mee;Nikita Merkulov;michaelhuawei Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label `openJiuwen-assistant` to the pull request, we will find and do it as soon as possible. --> What type of PR is this? <!-- Choose one label from `bug`, `task`, `feature` and `refactor`, and replace `<label>` below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append `/kind refactor` label after `/kind bug`, `/kind task` and `/kind feature`. --> /kind task What does this PR do / why do we need it: Added documentation for Importing an External Workflow, in Chinese and in English, including a step-by-step guide with pictures and a list of currently supported n8n node types. Which issue(s) this PR fixes: <!-- Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. --> Fixes [#796](https://gitcode.com/openJiuwen/agent-studio/issues/796) Code review checklist [[illustration]](https://gitcode.com/openJiuwen/community/blob/master/security/code_review_checklist_mechanism.md): ~~+ - [ ] whether to verify the function's return value (It is forbidden to use void to mask the return values of security functions and self-developed functions. C++ STL functions can be masked if there is no problem)~~ ~~+ - [ ] Whether to comply with SOLID principle / Demeter's law~~ ~~+ - [ ] Whether there is UT test case && the test case is a valid (if there is no test case, please explain the reason)~~ ~~+ - [ ] Whether the API change is involved~~ + - [x] Whether official document modification is involved <!-- Special notes for your reviewers*: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> See merge request: openJiuwen/agent-studio!982	1 个月前
开发工作流	Added documentation for Importing an External Workflow Co-authored-by: michaelhuawei<michael.atamuk@huawei.com> Co-authored-by: Nikita Merkulov<nikita.merkulov1@huawei.com> # message auto-generated for no-merge-commit merge: !982 merge doc-import-workflow into develop Added documentation for Importing an External Workflow Created-by: nikita-mee Commit-by: nikita-mee;Nikita Merkulov;michaelhuawei Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label `openJiuwen-assistant` to the pull request, we will find and do it as soon as possible. --> What type of PR is this? <!-- Choose one label from `bug`, `task`, `feature` and `refactor`, and replace `<label>` below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append `/kind refactor` label after `/kind bug`, `/kind task` and `/kind feature`. --> /kind task What does this PR do / why do we need it: Added documentation for Importing an External Workflow, in Chinese and in English, including a step-by-step guide with pictures and a list of currently supported n8n node types. Which issue(s) this PR fixes: <!-- Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. --> Fixes [#796](https://gitcode.com/openJiuwen/agent-studio/issues/796) Code review checklist [[illustration]](https://gitcode.com/openJiuwen/community/blob/master/security/code_review_checklist_mechanism.md): ~~+ - [ ] whether to verify the function's return value (It is forbidden to use void to mask the return values of security functions and self-developed functions. C++ STL functions can be masked if there is no problem)~~ ~~+ - [ ] Whether to comply with SOLID principle / Demeter's law~~ ~~+ - [ ] Whether there is UT test case && the test case is a valid (if there is no test case, please explain the reason)~~ ~~+ - [ ] Whether the API change is involved~~ + - [x] Whether official document modification is involved <!-- Special notes for your reviewers*: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> See merge request: openJiuwen/agent-studio!982	1 个月前
开发提示词	fix:jiaja2语法报错&部分环境高亮失效问题 Co-authored-by: wangxin<wangxin375@huawei.com> # message auto-generated for no-merge-commit merge: !925 fix:jiaja2语法报错&部分环境高亮失效问题 From: @programmegirl Reviewed-by: @xiaoyao42, @ZYQ5333 See merge request: openJiuwen/agent-studio!925	2 个月前
开发智能体	fix:增加runtime发布限制说明	1 个月前
README.md	refactor: move docs to studio Co-authored-by: 张雅晴<zhangyaqing8@huawei.com> # message auto-generated for no-merge-commit merge: !387 refactor: move docs to studio From: @ZYQ5333 Reviewed-by: @cyz95, @xiaoyao42 See merge request: openJiuwen/agent-studio!387	3 个月前
插件管理.md	Removing MCP option from plugin management Co-authored-by: Michael<michael.atamuk@huawei.com> # message auto-generated for no-merge-commit merge: !911 Removing MCP option from plugin management From: @michaelhuawei Reviewed-by: @xiaoyao42, @ZYQ5333 See merge request: openJiuwen/agent-studio!911	2 个月前
模型管理.md	adding clarification for ollama and non api-key providers Co-authored-by: @aharonamir1<amir.aharon@huawei.com> # message auto-generated for no-merge-commit merge: !674 merge my_develop into develop adding clarification for ollama and non api-key providers Created-by: aharonamir1 Commit-by: @aharonamir1 Merged-by: ZYQ5333 Description: <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/community/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label `openjiuwen-assistant` to the pull request, we will find and do it as soon as possible. --> What type of PR is this? <!-- 选择下面一种标签替换下方 `/kind <label>`，可选标签类型有： - /kind bug - /kind task - /kind feature - /kind refactor - /kind clean_code 如PR描述不符合规范，修改PR描述后需要/check-pr重新检查PR规范。 --> /kind feature Handles issue [#485](https://gitcode.com/openJiuwen/agent-studio/issues/485) Self-checklist:（请自检，在[ ]内打上x，我们将检视你的完成情况，否则会导致pr无法合入） + - [x] 设计：PR对应的方案是否已经经过Maintainer评审，方案检视意见是否均已答复并完成方案修改 + - [x] 测试：PR中的代码是否已有UT/ST测试用例进行充分的覆盖，新增测试用例是否随本PR一并上库或已经上库 + - [x] 验证：PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] 接口：是否涉及对外接口变更，相应变更已得到接口评审组织的通过，API对应的注释信息已经刷新正确 + - [x] 文档：是否涉及官网文档修改，如果涉及请及时提交资料到Doc仓 <!-- Special notes for your reviewers: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-studio!674	2 个月前
知识库管理.md	feat(kb): add new kb type weblink for frontend and backend Co-authored-by: Tinaxy<xinyu.hou2@h-partners.com> # message auto-generated for no-merge-commit merge: !813 feat(kb): add new kb type weblink for frontend and backend From: @Tinaxy Reviewed-by: @ZYQ5333, @cyz95, @xiaoyao42 See merge request: openJiuwen/agent-studio!813	2 个月前
记忆库管理.md	docs: fix docs directory structure Co-authored-by: yuzengjie01<yuzengjie@huawei.com> # message auto-generated for no-merge-commit merge: !622 docs: fix docs directory structure From: @yuzengjie01 Reviewed-by: @ZYQ5333, @xiaoyao42 See merge request: openJiuwen/agent-studio!622	3 个月前

开发指南