Skip to content

Workspace rules need a git remote, but learn status says "not linked" for a linked project #1663

Closed

Description

@sahrizvi

Found during the v0.12.9 end-to-end run (#1647).

Workspace rules are keyed by the project's git remote (rules/sync.ts: no_remote). In a project linked by path (no git remote):

  • learn status prints Workspace rules: not linked (run \altimate-code link`)althoughworkspace status` shows the project linked, so the suggested fix does nothing.
  • learn sync prints Rules sync skipped: this project has no git remote.
  • Adding a remote later and running link --workspace <id> --yes keeps the path binding (Matched by path), so rules stay off until the project is unlinked and linked again.
  • configure/learn.md doesn't say rules need a git remote.

Suggested: have learn status say rules need a git remote, document it, and let link move a path binding to the remote once one exists.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions