-
Notifications
You must be signed in to change notification settings - Fork 49
[SUP-2184] Only write local config in git repo #476
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
Conversation
mcncl
left a 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.
I think this will also cause issues on configure, where an API token will be required and not allow the user to configure with an incorrect one, but an API token should not be needed for certain commands, like bk pipeline validate.
Signed-off-by: Ben McNicholl <git@benmcnicholl.com>
PriyaSudip
left a 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.
Changes looks good, will wait for Test and Lint to go green.
Signed-off-by: Ben McNicholl <git@benmcnicholl.com>
Signed-off-by: Ben McNicholl <git@benmcnicholl.com>
This is not ready for merge!
Running the BK CLI tool from any directory will create a local config. This PR is to change this functionality so that it does not create the local config unless the directory is a valid git repo.