Skip to content

Fix public submodule metadata #33

@bordeauxred

Description

@bordeauxred

Why

Public clone/setup should not produce broken submodule metadata. Broken submodules create immediate friction for contributors and users trying benchmark integrations.

What

  • Run git submodule status --recursive and identify any missing .gitmodules mappings.
  • Decide which benchmark gitlinks are intentionally supported in the public repo.
  • Add missing .gitmodules entries or remove unsupported gitlinks.
  • Update README/examples if any unsupported benchmark paths are removed.

Acceptance

  • git submodule status --recursive exits without fatal errors.
  • Public docs do not require unsupported submodules.

Metadata

Metadata

Assignees

Labels

ai_tinker_launchAI Tinkerers newsletter launch readinessenhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions