Skip to content

chore(vendors): add Weave protocol - #388

Open
NWYLZW wants to merge 3 commits into
mainfrom
codex/add-weave-vendor
Open

chore(vendors): add Weave protocol#388
NWYLZW wants to merge 3 commits into
mainfrom
codex/add-weave-vendor

Conversation

@NWYLZW

@NWYLZW NWYLZW commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add the new public oneworks-ai/weave protocol repository as a vendor submodule.
  • Register the submodule at vendors/oneworks-ai/weave on branch main.

Changelog

  • Changelog path or "Not applicable": Not applicable

Screenshots

Not applicable

Validation

  • Verified oneworks-ai/weave is public with default branch main.
  • Verified the vendor gitlink points to ec356a726ddba653cca883a8ebbaf92839823f3e, matching oneworks-ai/weave remote main.
  • Ran git diff --cached --check before commit.
  • Ran SSH push dry-runs for both the new Weave repository and this vendor branch before actual pushes.

Review Scope

  • Risk: low
  • Applicable profiles: vendor submodule manifest update
  • Evidence: .gitmodules adds vendors/oneworks-ai/weave; gitlink mode is 160000.
  • Rule exceptions: none

Experience Review

  • 已判断是否需要沉淀经验
  • 如需要,已运行 $post-task-experience-review
  • reviewer PASS / NOT APPLICABLE 后才进入 merge

Policy Conflict Review

  • Not applicable: this PR only adds a vendor submodule manifest entry and gitlink.

@NWYLZW
NWYLZW requested a review from a team as a code owner August 19, 2026 21:33
@vercel

vercel Bot commented Aug 19, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
oneworks-dev Ignored Ignored Preview Aug 20, 2026 1:04pm

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Experience Review

Before merge, make sure the PR body contains this completed checklist:

## Experience Review
- [x] 已判断是否需要沉淀经验
- [x] 如需要,已运行 `$post-task-experience-review`
- [x] reviewer `PASS` / `NOT APPLICABLE` 后才进入 merge

Checklist to confirm:

  • Decide whether this PR produced reusable project experience.
  • If experience should be captured, run $post-task-experience-review.
  • Merge only after the independent reviewer reports PASS or NOT APPLICABLE for the Experience Review Result.
  • For workflow, permission, or release-rule documentation changes, also add this checked section to the PR body after an independent read-only conflict review:
## Policy Conflict Review
- [x] Independent read-only reviewer checked workflow, permission, and release-rule conflicts and reported PASS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant