-
-
Notifications
You must be signed in to change notification settings - Fork 160
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 multiple branches via "Profiles" feature #545
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
Instead of just selecting a branch a git repository could be assigned to a profile. This way a work repository could be shared with members from work without the risk to give them accidentally access to the private items (stored in a different git repository). |
Interesting idea @buepro. My use of pass has all been solo so I hadn't considered the use case you describe. Seems like a good thing to be mindful of though. |
The added paragraph shows how different git repositories can be used in profiles. Resolves: IJHack#545
The added paragraph shows how different git repositories can be used in profiles. Resolves: IJHack#545
My
pass
repo has mulitple branches -- one for personal items, one for work items. (I also have a 'common' branch for shared passwords, and inactive branches for old jobs in case I need e.g. previous health insurance info.)In the shell, this arrangement is easy enough to work with --
pass git checkout work
and so on.I'd love to have support for this in QtPass.
(The "profiles" feature could conceivably be used to do this if you had two clones of your repo, but that's sub-optimal.)
Here's my idea: in Profiles, in addition to "Name" and "Path", have a "Branch" field. If it's empty, QtPass just uses whatever branch is checked out (as it does now). If it has a value, that value is displayed in the "Select profile" menu (along with the Name), and selecting it switches to the specified branch.
If there's interest in this, I'm game for learning enough about the project source to try implementing it, or pairing up with someone else who's been wanting this.
The text was updated successfully, but these errors were encountered: