Skip to content

--interactive should actually default to true in user-facing situations. #48353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 14, 2025

Conversation

baronfel
Copy link
Member

@baronfel baronfel commented Apr 10, 2025

Ok this is embarrassing but when I did the --interactive defaulting I defaulted it to the wrong way around. Thankfully because today users have to pass --interactive to get the benefits there wasn't actually a regression.

I've fixed the conditional and updated the test baselines - the main changes here are that all of our CI tests have the false default because it's either a CI/CD system environment or the test is running redirected - so we really only have local testing to prove that this works:

image

@Copilot Copilot AI review requested due to automatic review settings April 10, 2025 15:32
@baronfel baronfel marked this pull request as draft April 10, 2025 15:32
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-CLI untriaged Request triage from a team member labels Apr 10, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

src/Cli/dotnet/CommonOptions.cs:135

  • The inline comment does not reflect the new logic of defaulting interactive mode to true when not running in a CI/redirected environment. Consider updating the comment to accurately describe the behavior.
              // this default is called when no tokens/options are passed on the CLI args

@baronfel baronfel force-pushed the actually-set-interactive-to-true branch from 6d73ffa to 39c3d8b Compare April 11, 2025 19:35
@baronfel baronfel requested a review from a team April 12, 2025 17:31
@baronfel baronfel merged commit c199edf into dotnet:main Apr 14, 2025
39 of 40 checks passed
@baronfel baronfel deleted the actually-set-interactive-to-true branch April 14, 2025 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-CLI untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants