You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One possibility to accomplish this would be to have a pearl.conf.d/ directory containing file for each new git repository. Addition and removal of git repositories would still be easy and there would be no interference with the user defined file pearl.conf which will still work seamlessly.
So, the pearl.conf file is a user defined config file, so it should not be managed by the pearl command itself. What I was thinking is to have a directory pearl.conf.d containing a file for each repository the user want to add. For instance, let's take the example in the documentation.
The user can type:
pearl add joe-dotfiles https://github.com/joe/mydotfiles.git "The Joe's dotfiles"
The description will be optional.
The script will create a file ~/.config/pearl/pearl.conf.d/joe-dotfiles containing:
I think it would be really helpful to allow installation of a git repository without having it in pearl.conf as a repository.
would be really useful.
Having Github organisation/repo as a shorthand script would be really useful as well.
Using
would be very helpful.
The text was updated successfully, but these errors were encountered: