Import dyad repository as a git submodule at third_party/dyad

[Copilot]

Adds the dyad repository as a git submodule for integration.

Changes

• Submodule: Added at third_party/dyad pointing to https://github.com/dyad-sh/dyad.git
• Documentation: Updated README.md with submodule initialization instructions
• License: Apache 2.0, available at third_party/dyad/LICENSE

After Cloning

git submodule update --init --recursive

CI/Build Implications

Pipelines should use --recurse-submodules when cloning or add the submodule init command to setup steps.

Original prompt

Import the external repository https://github.com/dyad-sh/dyad.git into the wasalstor-web/saas repository as a git submodule located at third_party/dyad.

Acceptance criteria:

• Create a new branch named import/dyad-submodule from the repository default branch (detect default branch automatically).
• Add the submodule pointing to https://github.com/dyad-sh/dyad.git at path third_party/dyad using the default branch HEAD of the dyad repo.
• Initialize and update any nested submodules inside dyad (git submodule update --init --recursive).
• Create or verify .gitmodules contains the correct entry for third_party/dyad.
• Update README.md to document the added submodule and include instructions to initialize and update submodules: git submodule update --init --recursive and note the submodule path and source repo.
• Ensure the dyad LICENSE is available in third_party/dyad/LICENSE (submodule contents) or add a top-level reference in LICENSE/NOTICE describing the included code and its license.
• Commit only the .gitmodules, README.md, and any top-level LICENSE/NOTICE changes. Do not modify unrelated files.
• Open a pull request titled "Import dyad repository as a git submodule at third_party/dyad" with a clear description including source repo URL, submodule path, branch created, and any build/runtime implications; include contribution checklist items if repository templates require them.

Fallback: If adding a submodule is blocked by repository policies (or submodule add fails), copy the dyad sources into third_party/dyad with attribution and include the dyad LICENSE file, then open the PR with explanation and license file included.

Do not modify unrelated files beyond README and top-level license/NOTICE files as needed. Make the PR easy for maintainers to review and accept the imported code.

This pull request was created as a result of the following prompt from Copilot chat.

Import the external repository https://github.com/dyad-sh/dyad.git into the wasalstor-web/saas repository as a git submodule located at third_party/dyad.

Acceptance criteria:

• Create a new branch named import/dyad-submodule from the repository default branch (detect default branch automatically).
• Add the submodule pointing to https://github.com/dyad-sh/dyad.git at path third_party/dyad using the default branch HEAD of the dyad repo.
• Initialize and update any nested submodules inside dyad (git submodule update --init --recursive).
• Create or verify .gitmodules contains the correct entry for third_party/dyad.
• Update README.md to document the added submodule and include instructions to initialize and update submodules: git submodule update --init --recursive and note the submodule path and source repo.
• Ensure the dyad LICENSE is available in third_party/dyad/LICENSE (submodule contents) or add a top-level reference in LICENSE/NOTICE describing the included code and its license.
• Commit only the .gitmodules, README.md, and any top-level LICENSE/NOTICE changes. Do not modify unrelated files.
• Open a pull request titled "Import dyad repository as a git submodule at third_party/dyad" with a clear description including source repo URL, submodule path, branch created, and any build/runtime implications; include contribution checklist items if repository templates require them.

Fallback: If adding a submodule is blocked by repository policies (or submodule add fails), copy the dyad sources into third_party/dyad with attribution and include the dyad LICENSE file, then open the PR with explanation and license file included.

Do not modify unrelated files beyond README and top-level license/NOTICE files as needed. Make the PR easy for maintainers to review and accept the imported code.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.