I found shellbit interesting and I'm trying to incorporate it in my projects, but I found the 'project' and 'version' discovery to be troublesome. To migrate my project setups to shellbit, I need to develop the nix setups, and I would prefer to use just the latest (master) at the moment, but shellbit requires a specific tag. The other problem is that when I'm starting a new project, it doesn't have to be a git repository, or must have a remote configured.
Shellbit will work better for me, if it would use its config file to store which version and project should be used for a given root path (just like the initial repo configuration) and to support non tagged versions (commit sha and branches).
I found shellbit interesting and I'm trying to incorporate it in my projects, but I found the 'project' and 'version' discovery to be troublesome. To migrate my project setups to shellbit, I need to develop the nix setups, and I would prefer to use just the latest (master) at the moment, but shellbit requires a specific tag. The other problem is that when I'm starting a new project, it doesn't have to be a git repository, or must have a remote configured.
Shellbit will work better for me, if it would use its config file to store which version and project should be used for a given root path (just like the initial repo configuration) and to support non tagged versions (commit sha and branches).