basher list doesn't handle deeper directory structures

[nhomble]

I've been hosting some scripts in a gitlab organization which doesn't follow the nice username/project structure we have in github. It's more like org/group/function/repo.

When I do basher list, I only get part of the path which means basher upgrade trivially succeeds cause it doesn't find the git project to pull.

My current workaround is to manually pull in the basher cellar.

Looking at the implementation, the assumption looks to be in the package_path loop in basher-list

for package_path in "${BASHER_PACKAGES_PATH}"/*/*
.
.
.

--
@juanibiapina maybe we can come up with a better list of git repos with find?

[juanibiapina]

Yeah, or a better glob pattern.