Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print a concise summary of Scorecard metrics when the --scoring flag is passed on thamos advise #1149

Closed
Tracked by #434 ...
goern opened this issue Jul 28, 2022 · 5 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.

Comments

@goern
Copy link
Member

goern commented Jul 28, 2022

In the context of thoth-station/core#434

PoC: Implement an experimental thamos flag on the advise command to give users insights about the maintenance of their packages

@sesheta
Copy link
Member

sesheta commented Jul 28, 2022

@goern: This issue is currently awaiting triage.
If a refinement session determines this is a relevant issue, it will accept the issue by applying the
triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label Jul 28, 2022
@sesheta
Copy link
Member

sesheta commented Jul 28, 2022

@goern: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>

Please see the group list for a listing of the SIGs, and working groups available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@mayaCostantini
Copy link
Contributor

/sig stack-guidance
/priority critical-urgent

@sesheta sesheta added sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Aug 9, 2022
@mayaCostantini mayaCostantini self-assigned this Aug 9, 2022
@mayaCostantini mayaCostantini changed the title Print a concise summary with those metrics when the flag is passed Print a concise summary of Scorecard metrics when the --scoring flag is passed on thamos advise Aug 9, 2022
@goern
Copy link
Member Author

goern commented Aug 9, 2022

/kind feature

@sesheta sesheta added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 9, 2022
@mayaCostantini mayaCostantini removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. needs-sig labels Aug 9, 2022
@codificat codificat moved this to 🏗 In progress in Planning Board Sep 24, 2022
@mayaCostantini
Copy link
Contributor

Let's close this issue as this feature was implemented in #1155.
The evolution of the scoring logic can be tracked by thoth-station/core#434.

Repository owner moved this from Sprint Backlog to Done in [OSG][SCRUM][Project OSG] Oct 3, 2022
Repository owner moved this from 🏗 In progress to ✅ Done in Planning Board Oct 3, 2022
@schwesig schwesig moved this from Done to Closed in [OSG][SCRUM][Project OSG] Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.
Projects
Status: Done
Development

No branches or pull requests

3 participants