Bug 2099582 - Format and update Repository overview content
Summary: Format and update Repository overview content
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.11
Hardware: All
OS: All
Target Milestone: ---
: 4.11.0
Assignee: Karthik Jeeyar
QA Contact: spathak@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2022-06-21 09:42 UTC by Karthik Jeeyar
Modified: 2022-08-10 11:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:18:49 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11737 0 None open Bug 2099582: Format and update the repository overview page 2022-06-21 10:05:32 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:18:58 UTC

Description Karthik Jeeyar 2022-06-21 09:42:48 UTC
Description of problem:

format all directory, filenames and CLI commands as inline code and update the steps content

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install Openshift Pipelines.
2. Create Repository, and you will be landed in overview page.

Actual results:

`Step 4` title needs to be dropped and format all the directory, filenames and cli commands. 

Expected results:
The overview page content needs to be updated and formatted.

Comment 5 Hemant Saini 2022-06-24 10:41:58 UTC
verified on build version: 4.11.0-0.nightly-2022-06-23-153912
verified on browser version: chrome 102

Comment 6 errata-xmlrpc 2022-08-10 11:18:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.