-
Notifications
You must be signed in to change notification settings - Fork 33
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
support a config file #72
Comments
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i have a few of projects that need to prevent updates for a couple of pinned dependencies. i'm able to do this with
updtr
if i remember to provide the--exclude
flag. the problem, though, is remembering to do that.it would be great if i could capture config that i need to use repeatedly per project in a way that could be versioned with the project.
i've seen that a number of projects are now using cosmic-config to simplify getting config info into cli-based apps and make it flexible for consumers to decisde where they define their config. personally, i've given up on keeping the root of my projects clear of config files, so i'd be happy to add a
.updtrrc
to my collection of rc files that already litters all of my projects.would something along these lines be possible to save us from forgetting to provide config directly on the cli?
The text was updated successfully, but these errors were encountered: