I think flow should
a) respect the default setting from the project
b) ask the user if there is a fork relation set up
Marcel (753270c3) at 06 Mar 09:32
feat: get count of tokens
superseded by gitlab-org/cli!2942
part of #8196
Resolves #[issue_number]
Marcel (58fdcb2a) at 06 Mar 09:23
feat: get count of tokens
closed because as mentioned by @phikai in the issue, this is same same to token ... will refine the issue and will create a new PR
Marcel (058a5fa7) at 05 Mar 15:48
added tests - but already get the point is doing the same same ......
you are totally right .. sorry, missed that token command ;/ vibe coded it faster than reading the doc
I'll refine this and the issue, indeed there are some cases missing. starting with tokens for audit was just one, I assume to add audit as a summary for different "security configuration" related things.
I'll be back ... refined the issue
ok, just for clarification (you already mentioned it above "after configuring ssh_host"):
neither !2888 (merged) fixed auto-adding the ssh_host even ssh is detected nor there is a successor issue / PR of gitlab-community/gitlab-org/cli!8 (closed) , is there?
actually with PR !2924 (merged) it is functional but flow for setup is still someway unlucky needing the user to manually post-configure after auth login where !2928 (merged) comes in, right?
Marcel (4da37e2a) at 04 Mar 15:18
feature: gitlab-org/cli/-/issues/8196 glab audit
Marcel (d3175ba8) at 04 Mar 15:09
feature: gitlab-org/cli/-/issues/8196 glab audit
... and 1 more commit
can't add
/label ~"group::pipeline execution" ~"Category:Continuous Integration" ~"section::ci" ~"devops::verify" ~"workflow::planning breakdown" ~"needs weight" ~"cicd::planning" ~"needs investigation" ~"type::bug" ~"feature flag" ~documentation
/milestone %"Backlog"
@marknuzzo What are we expecting to happen?