Skip to content

Conversation

@rhamilto
Copy link
Member

@rhamilto rhamilto commented Jan 12, 2026

…appropriate

Summary by CodeRabbit

  • Tests
    • Updated Cypress integration tests to reflect unified terminology (OperatorHub → Operator/Software Catalog).
    • Renamed test identifiers for consistency across operator-related suites.
    • Standardized test descriptions, log messages, and assertions for clearer, consistent wording.
    • Minor non-functional text and comment adjustments to improve readability.

✏️ Tip: You can customize this high-level summary in your review settings.

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 12, 2026
@openshift-ci-robot
Copy link
Contributor

@rhamilto: This pull request references Jira Issue OCPBUGS-72571, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

…appropriate

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 openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai
Copy link

coderabbitai bot commented Jan 12, 2026

Walkthrough

Tests and a view helper were updated for naming consistency: capitalization and terminology changes in multiple Cypress tests, plus a parameter/property rename from operatorHubCardTestIDoperatorCardTestID in operator view and test usages. No behavioral test flows were altered.

Changes

Cohort / File(s) Summary
Test string/capitalization updates
frontend/packages/integration-tests-cypress/tests/app/auth-multiuser-login.cy.ts, frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/catalog-source-details.cy.ts, frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/edit-default-sources.cy.ts, frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-hub.cy.ts
Updated descriptive strings, comments, and assertion messages for consistent capitalization/terminology (e.g., operatorHubOperatorHub, suite titles referencing Operators). No control-flow changes.
Test property rename (install/uninstall tests)
frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-global.cy.ts, frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-single-namespace.cy.ts, frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-uninstall.cy.ts
Renamed testOperator.operatorHubCardTestIDtestOperator.operatorCardTestID and updated all call sites to pass the new property. Changes confined to test data and install/uninstall invocations.
Deprecated operator warnings test updates
frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/deprecated-operator-warnings.cy.ts
Standardized test descriptions, logs, and assertions to use consistent terminology (e.g., "Operator tile"/"Operator details panel"); removed operatorHubCardTestID from test data. No logic changes.
Operator view public API change
frontend/packages/operator-lifecycle-manager/integration-tests-cypress/views/operator.view.ts
Renamed parameter in exported install function: operatorHubCardTestIDoperatorCardTestID, and updated internal selector usage accordingly. This alters the function signature used by tests.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: removing 'OperatorHub' references from OLM integration tests and standardizing terminology across multiple test files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

Comment @coderabbitai help to get the list of available commands and usage tips.

@rhamilto
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 12, 2026
@openshift-ci-robot
Copy link
Contributor

@rhamilto: This pull request references Jira Issue OCPBUGS-72571, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from yapei January 12, 2026 20:18
@openshift-ci-robot
Copy link
Contributor

@rhamilto: This pull request references Jira Issue OCPBUGS-72571, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

Details

In response to this:

…appropriate

Summary by CodeRabbit

  • Tests
  • Updated Cypress integration tests to reflect terminology standardization (OperatorHub references updated).
  • Refactored test identifiers and navigation assertions for consistency.
  • Standardized test descriptions and labels across operator-related test suites.

✏️ Tip: You can customize this high-level summary in your review settings.

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 openshift-eng/jira-lifecycle-plugin repository.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🤖 Fix all issues with AI agents
In
@frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/deprecated-operator-warnings.cy.ts:
- Line 115: The test title string in the it(...) call currently contains a typo
"deprectaed"; update the description to "verify deprecated version warnings in
the Operator details panel" by editing the it('verify deprectaed version
warnings in the Operator details panel', ...) invocation to correct "deprectaed"
→ "deprecated" so the test name reads "verify deprecated version warnings in the
Operator details panel".

In
@frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-global.cy.ts:
- Around line 4-7: The test fails because operator.install still expects the old
parameter name operatorHubCardTestID; update the operator.install function
signature in operator.view.ts to replace operatorHubCardTestID with
operatorCardTestID, and update any internal references (e.g., the
cy.byTestID(...) call) to use operatorCardTestID so the call
operator.install(testOperator.name, testOperator.operatorCardTestID, ...)
matches the function parameters.

In
@frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-single-namespace.cy.ts:
- Around line 6-10: The install() signature in operator.view.ts still uses the
old parameter name operatorHubCardTestID; update its parameter list to replace
operatorHubCardTestID with operatorCardTestID and keep the rest unchanged
(operatorName: string, operatorCardTestID: string, installToNamespace: string =
GlobalInstalledNamespace, useOperatorRecommendedNamespace: boolean = false) so
the view layer matches the renamed test property used by
operator-install-single-namespace.cy.ts, operator-install-global.cy.ts and
operator-uninstall.cy.ts.
🧹 Nitpick comments (1)
frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/deprecated-operator-warnings.cy.ts (1)

191-241: LGTM with a minor note on capitalization consistency.

The test logic and assertions are correct. However, these test descriptions use lowercase "operator" (e.g., "deprecated operator warnings") while earlier tests use "Operator" with a capital O (e.g., "deprecated Operator warnings" on lines 55, 77, 141, 162). Consider aligning capitalization across all test descriptions for consistency, though this is a nitpick.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 54bb8be and 610771a.

📒 Files selected for processing (8)
  • frontend/packages/integration-tests-cypress/tests/app/auth-multiuser-login.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/catalog-source-details.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/deprecated-operator-warnings.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/edit-default-sources.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-hub.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-global.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-single-namespace.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-uninstall.cy.ts
🧰 Additional context used
🧬 Code graph analysis (2)
frontend/packages/integration-tests-cypress/tests/app/auth-multiuser-login.cy.ts (1)
frontend/packages/integration-tests-cypress/views/nav.ts (1)
  • nav (6-105)
frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/deprecated-operator-warnings.cy.ts (1)
frontend/packages/operator-lifecycle-manager/integration-tests-cypress/views/operator.view.ts (1)
  • operator (11-214)
🔇 Additional comments (10)
frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/deprecated-operator-warnings.cy.ts (5)

55-75: LGTM!

Test description properly updated from "OperatorHub tile" to "Operator tile" — aligns with the broader terminology normalization effort. Test logic remains intact and correctly verifies the deprecated badge on the catalog tile.


77-88: LGTM!

Terminology updated to "Operator details panel" — consistent with the PR's goal. Test assertions for the deprecated badge and package warning message are appropriate.


90-113: LGTM!

Description updated appropriately. The test correctly exercises the channel selection flow and verifies deprecation warning icons and messages appear as expected.


141-160: LGTM!

Test description and log messages updated to reflect "Install Operator details page" terminology. The assertions correctly verify all three deprecation warning types (package, channel, version) on the subscription page.


162-189: LGTM!

Terminology normalized in both the test description and log messages. The test flow correctly exercises the full installation approval path and verifies the deprecated badge appears on the Installed Operators page.

frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/catalog-source-details.cy.ts (1)

26-27: LGTM - Capitalization consistency fix.

The comment now correctly capitalizes "OperatorHub" as a proper noun, consistent with the selector on line 24 and the section header assertion on line 27.

Side note: The pre-existing typo "verfiy" remains on lines 26, 44, and 85 — consider fixing those in a follow-up if you're tidying up comments.

frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-hub.cy.ts (1)

3-3: LGTM - Test descriptions updated to match new terminology.

The suite and test descriptions are updated consistently:

  • Suite: "Interacting with Operators" accurately describes the test scope
  • Test: "Operator catalog items" aligns with the actual test behavior

The test assertions (line 20: 'Software Catalog' heading) and navigation remain consistent with the updated terminology across the PR.

Also applies to: 17-17

frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/edit-default-sources.cy.ts (1)

18-25: LGTM - Capitalization standardized for OperatorHub references.

Good judgment here — this test specifically exercises the OperatorHub configuration/details page, so retaining "OperatorHub" in the descriptions is appropriate. The capitalization is now consistent with:

  • The legacy test ID selector: cy.byLegacyTestID('OperatorHub') (line 22)
  • The section header assertion: 'OperatorHub details' (line 25)

Same "verfiy" typo note as the other file — a quick find/replace would clean those up across the test suite.

frontend/packages/integration-tests-cypress/tests/app/auth-multiuser-login.cy.ts (1)

44-45: Navigation item name is correctly updated to "Software Catalog".

The test assertion is accurate. The console-extensions.json confirms this nav item is defined with "section": "ecosystem" and "perspective": "admin", making it an admin-only section. The change from "OperatorHub" to "Software Catalog" reflects the actual current UI naming across all locales (EN, JA, ZH, FR, ES), with backward compatibility maintained through path routing that still recognizes the old "operatorhub" paths. The test logic correctly validates that non-admin users lack access to this admin-scoped navigation item.

frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-uninstall.cy.ts (1)

6-10: Rename applied correctly in both definition and usage.

The operatorCardTestID property rename (line 8) and its corresponding usage in operator.install() (line 30) are consistent. The remainder of the test logic—including the uninstall modal interactions, intercepts, and operand lifecycle assertions—is unaffected by this terminology change.

Also applies to: 28-32

Comment on lines 4 to 7
const testOperator = {
name: 'Data Grid',
operatorHubCardTestID: 'operator-Data Grid',
operatorCardTestID: 'operator-Data Grid',
};
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for remaining operatorHubCardTestID references (deprecated)
echo "=== Checking for remaining 'operatorHubCardTestID' references ==="
rg 'operatorHubCardTestID' --type ts || echo "✓ No deprecated references found"

echo ""
echo "=== Verifying 'operatorCardTestID' usage across test files ==="
rg 'operatorCardTestID' --type ts -l

echo ""
echo "=== Checking operator.install() signature in operator.view ==="
fd 'operator.view.ts' -x head -100 {}

Repository: openshift/console

Length of output: 5856


Parameter name mismatch breaks the test—operator.view.ts signature must be updated.

The refactor is incomplete. While this file correctly renamed the property from operatorHubCardTestID to operatorCardTestID, the operator.install() function in operator.view.ts still expects the old parameter name operatorHubCardTestID. The test will fail when calling operator.install(testOperator.name, testOperator.operatorCardTestID, ...) because the function signature hasn't been updated to match.

Update the operator.install() signature and its usages in operator.view.ts to use operatorCardTestID instead of operatorHubCardTestID. This affects the function parameter declaration and the internal cy.byTestID(operatorCardTestID) call.

🤖 Prompt for AI Agents
In
@frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-global.cy.ts
around lines 4 - 7, The test fails because operator.install still expects the
old parameter name operatorHubCardTestID; update the operator.install function
signature in operator.view.ts to replace operatorHubCardTestID with
operatorCardTestID, and update any internal references (e.g., the
cy.byTestID(...) call) to use operatorCardTestID so the call
operator.install(testOperator.name, testOperator.operatorCardTestID, ...)
matches the function parameters.

@openshift-ci openshift-ci bot added component/olm Related to OLM kind/cypress Related to Cypress e2e integration testing approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 12, 2026
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/edit-default-sources.cy.ts (1)

18-25: Capitalization standardization looks good.

The terminology changes correctly capitalize "OperatorHub" as a proper noun, consistent with OpenShift product naming conventions. The test title and log message now align with how this feature is referenced elsewhere in the UI.

One minor nit: line 24 has a pre-existing typo "verfiy" → "verify". Since you're already touching this area, might be worth fixing opportunistically.

📝 Optional typo fix
-    // verfiy OperatorHub details page is open
+    // verify OperatorHub details page is open
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 610771a and 2d8f225.

📒 Files selected for processing (9)
  • frontend/packages/integration-tests-cypress/tests/app/auth-multiuser-login.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/catalog-source-details.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/deprecated-operator-warnings.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/edit-default-sources.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-hub.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-global.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-single-namespace.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-uninstall.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/views/operator.view.ts
🚧 Files skipped from review as they are similar to previous changes (5)
  • frontend/packages/integration-tests-cypress/tests/app/auth-multiuser-login.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-global.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/deprecated-operator-warnings.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/catalog-source-details.cy.ts
  • frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-hub.cy.ts
🔇 Additional comments (5)
frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-uninstall.cy.ts (2)

6-10: LGTM – test object aligns with updated install signature.

The testOperator property rename to operatorCardTestID (line 8) correctly reflects the terminology change and matches the updated operator.install parameter name.


28-32: LGTM – install call correctly references renamed property.

The operator.install invocation now passes testOperator.operatorCardTestID (line 30), properly aligned with both the updated function signature and the object property rename. No functional change, just naming consistency.

frontend/packages/operator-lifecycle-manager/integration-tests-cypress/tests/operator-install-single-namespace.cy.ts (2)

6-10: LGTM – consistent rename across test fixtures.

The operatorCardTestID property (line 8) follows the same pattern as other test files in this PR. Good consistency.


35-39: LGTM – install invocation correctly updated.

The operator.install call (line 37) properly uses the renamed testOperator.operatorCardTestID. The test flow is unchanged; only the identifier naming is standardized.

frontend/packages/operator-lifecycle-manager/integration-tests-cypress/views/operator.view.ts (1)

12-23: Clean parameter rename with full caller coverage.

The operatorHubCardTestIDoperatorCardTestID rename is properly implemented and consistent. All three call sites have been updated: operator-install-global.cy.ts, operator-install-single-namespace.cy.ts, and operator-uninstall.cy.ts correctly pass testOperator.operatorCardTestID. No stale references remain.

@rhamilto
Copy link
Member Author

/retest

4 similar comments
@rhamilto
Copy link
Member Author

/retest

@rhamilto
Copy link
Member Author

/retest

@rhamilto
Copy link
Member Author

/retest

@rhamilto
Copy link
Member Author

/retest

@rhamilto
Copy link
Member Author

/assign @TheRealJon
/assign @yapei

@rhamilto
Copy link
Member Author

/retest

1 similar comment
@rhamilto
Copy link
Member Author

/retest

@yapei
Copy link
Contributor

yapei commented Jan 14, 2026

The text changes look good to me and pass in CI
/verified by @yapei and CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 14, 2026
@openshift-ci-robot
Copy link
Contributor

@yapei: This PR has been marked as verified by @yapei.

Details

In response to this:

The text changes look good to me and pass in CI
/verified by @yapei

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 openshift-eng/jira-lifecycle-plugin repository.

@rhamilto
Copy link
Member Author

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Jan 14, 2026
Copy link
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 14, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, rhamilto

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 8c6b5f8 and 2 for PR HEAD 2d8f225 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2026

@rhamilto: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 5ada2bf into openshift:main Jan 14, 2026
8 checks passed
@openshift-ci-robot
Copy link
Contributor

@rhamilto: Jira Issue Verification Checks: Jira Issue OCPBUGS-72571
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-72571 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

…appropriate

Summary by CodeRabbit

  • Tests
  • Updated Cypress integration tests to reflect unified terminology (OperatorHub → Operator/Software Catalog).
  • Renamed test identifiers for consistency across operator-related suites.
  • Standardized test descriptions, log messages, and assertions for clearer, consistent wording.
  • Minor non-functional text and comment adjustments to improve readability.

✏️ Tip: You can customize this high-level summary in your review settings.

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 openshift-eng/jira-lifecycle-plugin repository.

@rhamilto rhamilto deleted the OCPBUGS-72571 branch January 14, 2026 17:52
@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.22.0-0.nightly-2026-01-19-085729

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

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. component/olm Related to OLM jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/cypress Related to Cypress e2e integration testing lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants