-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Feature/flag quiet #185
Feature/flag quiet #185
Conversation
🙏 Thanks for opening this pull request! Please check out our contributing guidelines. |
🙏 Thank your for raising your pull request. |
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.
@ashupatil96 Thanks for the PR.
- Please address comments & let me know if you any questions!
Here is an overview of what got changed by this pull request: Issues
======
- Added 1
See the complete overview on Codacy |
Let me know if you need any help from my side. |
@gopinath-langote Please Review. |
@ashupatil96 LGTM. Thanks for the PR. This was a long waiting feature for me. |
Congrats on merging your first pull request! We here at 1build are proud of you! 🙏 |
Description
Sometimes developers choose to not see all logs/output of your command and just see success or failure as the outcome. Hence adding --quiet or -q flag to 1build command execution will result in just executing the command but not showing the entire output of it.
Fixes/Implements: #140
New dependencies introduced
Reason: Viper has the ability to bind to flags. To bind flag --quiet flag throughout project(particularly exec.go)
Checklist