Skip to content
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 using a config file in ~/.config if no config file is given on the command line #53

Open
jwodder opened this issue May 1, 2024 · 0 comments
Labels
breaking change Introduction of an incompatible API change cmd:apply Relates to the `apply` subcommand configuration Relates to labelmaker configuration files enhancement New feature or request therefor under consideration Dev has not yet decided whether or how to implement

Comments

@jwodder
Copy link
Owner

jwodder commented May 1, 2024

This would be a breaking change to apply, as its command-line usage would have to take the config file as an option rather than a non-option argument.

See https://stackoverflow.com/a/76341487/744178 regarding using a dynamic path (likely from dirs or similar) as the default config file path.

On the other hand, the whole motivation for this issue is so that I can run labelmaker without having to cd into the directory where I store my config file, but I'd still need a place to store my list of labelmaker-managed repositories, and moving the list to the config file after implementing #19 would just make it harder to automatically regenerate the list (unless I use toml_edit to preserve the formatting...), so maybe I'm doomed to always cd somewhere anyway.

@jwodder jwodder added cmd:apply Relates to the `apply` subcommand configuration Relates to labelmaker configuration files under consideration Dev has not yet decided whether or how to implement breaking change Introduction of an incompatible API change enhancement New feature or request therefor labels May 1, 2024
@jwodder jwodder added high priority Work on these first and removed high priority Work on these first labels Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Introduction of an incompatible API change cmd:apply Relates to the `apply` subcommand configuration Relates to labelmaker configuration files enhancement New feature or request therefor under consideration Dev has not yet decided whether or how to implement
Projects
None yet
Development

No branches or pull requests

1 participant