Skip to content

Conversation

@pabel-rh
Copy link
Member

@pabel-rh pabel-rh commented Oct 29, 2025

IMPORTANT: Do Not Merge - To be merged by Docs Team Only

Version(s):
1.8, main
Issue:
RHIDP-8709
Preview:
https://redhat-developer.github.io/red-hat-developers-documentation-rhdh/pr-1465/scorecard-plugin/

@rhdh-bot
Copy link
Collaborator

rhdh-bot commented Oct 29, 2025

@dzemanov
Copy link
Member

Thank you @pabel-rh for the PR, I have requested some changes but we are almost there.
I think it would also be good to add 1 screenshot of how scorecards look like. You can screenshot some from feature demo or you can use this one:
Screenshot 2025-10-30 at 11 40 47

@pabel-rh pabel-rh added Technical review done ⛅ Any procedure has been succesfully tested and removed Technical review needed 🔩 Test all the procedures labels Oct 30, 2025
@pabel-rh pabel-rh added Technical review needed 🔩 Test all the procedures and removed Technical review done ⛅ Any procedure has been succesfully tested labels Nov 3, 2025
@pabel-rh pabel-rh added Technical review done ⛅ Any procedure has been succesfully tested and removed Technical review needed 🔩 Test all the procedures labels Nov 4, 2025
:_mod-docs-content-type: CONCEPT

[id="con-best-practices-for-threshold-rules"]
= Best practices for threshold rules
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are threshold rules? have we defined it anywhere?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, Shipra. This topic appears after the definition. Adding an image of the doc preview from GitHub:
image

[id="proc-installing-scorecard-plugin-in-rhdh-instance_{context}"]
= Installing the Scorecard plugin in your {product} instance

You must manually install and enable the plugin in your {product} instance.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why users would need to perform this procedure? What's the benefit?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is like a whole module. So, its benefits and all are mentioned in the conceptual topics in the beginning of this assembly. Adding a screenshot of the above concept:
image

[id="proc-viewing-scorecards-in-rhdh_{context}"]
= Viewing Scorecard metrics in {product}

As a developer, you can view the GitHub and Jira metrics using the *Scorecards* in your {product-very-short} instance.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why users would need to perform this procedure? What's the benefit?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is mentioned in the main module on top. These procedures are a subset of the main module which explains why this is beneficial.

. In your {product-very-short} navigation menu, go to *Catalog*.
. Select the software component (catalog entity) that has Scorecard metrics configured.
. On the component *Service* page, go to the **Scorecard** tab.
. To view the desired metrics, select the corresponding tile. No newline at end of file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add a screenshot here for reference?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have a screenshot reference right at the top during the explanation, Shipra..
Adding image:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants