Replies: 1 comment
-
|
While this is a nice and valid feature request, I feel that the Btw: this reminds of (disclaimer: I've never committed (yet) to this project; these are only my 2cents as a dev) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
I work on a few different Jira projects within the same org. The auth, server, login, etc. are the same everywhere — only the default project (and sometimes the board) changes depending on what I'm working on.
Right now to switch projects I have to either pass
-p PROJon every command, duplicate my full config and use--config/JIRA_CONFIG_FILE, or set up direnv. Duplicating the full config is annoying because if I rotate my token or change anything else, I have to update every file.Describe the solution you'd like
Look for a
.jira-config.ymlin the current directory and walk up until one is found, like git does with.git/. If found, merge it on top of the global config — local values win, missing values are inherited.Typical local file would just be:
No need to repeat server, login, auth_type, etc.
Describe alternatives you've considered
-pon every command — tedious, and doesn't cover the board--config/JIRA_CONFIG_FILE— works but painful to keep in syncI've started a PR for this, fill free to comment it
Beta Was this translation helpful? Give feedback.
All reactions