You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f693537
Browse filesBrowse the repository at this point in the historyBrowse files
feat(core): say which values came from the project config file
When a command takes its organization or project from .cs-launch.json
instead of a flag, it now prints one line before anything else:
Using the organization and project UIDs from /path/to/.cs-launch.json.
so a user in a linked folder can see where the target came from - most
usefully just above the projects:delete question. With one value it
reads "Using the project UID from ...". Nothing is printed when every
value came from a flag, a prompt or a default.
- resolveInputsTraced returns the sources map the resolver already
built and discarded; resolveInputs keeps its signature on top of it.
- Each config-backed resolution spec declares a configLabel
(organization, project); resources.test.ts fails if one is missing, so
a future config key cannot drop out of the notice.
- configSourceNotice words the line from those labels and the full path
of the file actually read (a relative --config is resolved first).
- LaunchCommand.init prints it through ux.print, like every other line.
Only the path is cyan, and only when stdout is a terminal - green
reads as success and yellow as a warning here. No info: prefix.
The project-folder integration test now expects the notice as the first
line of stdout. AGENTS.md documents the notice and configLabel, and the
.talismanrc checksums are refreshed for the touched files, and
src/core/resolve.ts gets a checksum entry: Talisman flags its FlagKey /
resolutionTable lines as key-shaped, none of which is a secret.
#claude_code#
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
0 commit comments