-
Notifications
You must be signed in to change notification settings - Fork 3.7k
fix: simpler dangerous command warning #7987
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
fix: simpler dangerous command warning #7987
Conversation
|
💡 To request a new review, comment |
AI Code ReviewAI review failed due to service initialization issues. Please check the Continue API key and configuration. No specific line comments generated. 💡 To request a new detailed review, comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 1 file
|
🎉 This PR is included in version 1.23.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.21.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Dangerous command warning is pretty long and noisy in long chats. Simplify
Summary by cubic
Simplified the dangerous command warning to a short “Potentially dangerous command” message in the pre-toolbar to reduce noise in long chats. Also cleaned up the import placement for evaluateTerminalCommandSecurity.