Closed ljharb closed 2 years ago
Yup absolutely! Running repo-report
should default to detail
imo. I'm also in favour of removing options
but I kinda like the list
command. detail
is huuge and I think sometimes its useful to just see all of my repos with the access I have (and maybe defbranch?). I was also thinking we should rename it to ls
.
Also, I'm not sure if the ls
command is a good use-case for the target users. Just that I kinda like it :)
Is there an option that could be passed to detail that limited it just to the metrics list displays?
detail -p DefBranch -p Access --actual
comes close. But with #46, we'll need to pass in all focus filters too. Also these will be grouped so it's not one repo per row like in list
.
Maybe removing default branch and access from list
by default, and requiring -p to specify what’s included, would make sense?
That way, by default it really is just a list of repos.
Yup that makes sense. But I don't think we should give the -p flag. That's essentially the same as detail -p
.
This way we can have 2 use-cases:
repo-report
repo-report ls
I'm not really sure if ls
is required tho. repo-report ls
doesn't sound right.
Having -p be the same as list is what I’m suggesting :-) namely, that list is a shortcut for “detail, but default to no metrics”
Should ls
be allowed to take in all flags that detail
does or none? 🤔
Probably most? it's really just a wrapper around detail
with some specific args, no?
Got it! Just wanted to make sure I understood it correctly.
Fixed in #48.
Do we want to keep
list
andoptions
andbranchProtections
? They both kind of seem like subsets ofdetail
to me.Also, the
pr-status
command seems like maybe it should be a separate project (a separate one already exists, also not yet public).If in fact all of these can/should be dropped or moved to another project, then perhaps we could make
detail
be the default command?