# docs(resolveref): fix misleading --org hint in project ambiguity error

`c5d1bcc`·

toothbrush·3w ago·1 file·+4 added/-2 removed

The project-name ambiguity error told users to "scope with --org", but resolveProjectRef's callers (repo create/list, grant project …) have no --org flag — only `entire project list` does. Point users at the listed ULIDs and at `entire project list --org <org>` to find one. Keeps behavior identical; addresses PR #1498 review (Copilot).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## Sessions

8f880a0863f7View transcript

## Changes

1

- cmd/entire/cli

- Mresolveref.go+4/-2

```
121 unmodified lines

122
123
124
125
125
126
127
128
129
130
11 unmodified lines

142
143
144
143
145
146
147
148

121 unmodified lines

// pickProject selects the single project named name. Project names are unique
// only within an owner, so a bare name can match several projects across
// different orgs/accounts; on ambiguity the candidates (id + owner) are listed
// so the user can pass the ULID or scope by org.
// so the user can pass the intended ULID. (We can't suggest re-scoping the
// failing command: resolveProjectRef's callers — repo create/list, grant
// project … — have no --org flag; only `entire project list` does.)
func pickProject(projects []coreapi.Project, name string) (string, error) {
	var matches []coreapi.Project
	for _, p := range projects {
11 unmodified lines

for i, p := range matches {
			parts[i] = fmt.Sprintf("%s (owner %s)", p.ID, p.OwnerId)
		}
		return "", fmt.Errorf("project name %q is ambiguous (%s); pass a ULID or scope with --org", name, strings.Join(parts, ", "))
		return "", fmt.Errorf("project name %q is ambiguous (%s); pass the intended ULID (run `entire project list --org <org>` to find it)", name, strings.Join(parts, ", "))
	}
}
```

Mcmd/entire/cli/resolveref.go+4/-2