Skip to content

OCPBUGS-109743: Derive console notification docs URL from cluster version - #1676

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
lucaconsalvi:fix/ocpedge-2916-console-docs-link
Aug 17, 2026
Merged

OCPBUGS-109743: Derive console notification docs URL from cluster version#1676
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
lucaconsalvi:fix/ocpedge-2916-console-docs-link

Conversation

@lucaconsalvi

@lucaconsalvi lucaconsalvi commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Summary

  • The docsBasePath constant in consolenotification.go was hardcoded to 4.22, so console notification banners (degraded recovery, troubleshooting) always linked to 4.22 docs regardless of the actual cluster version
  • Derives the docs URL version dynamically from ClusterVersion.Status.History[0].Version at runtime, with a "latest" fallback when ClusterVersion is unavailable
  • Follows the same pattern used by MCO (pkg/operator/status.go)

Changes

File Change
pkg/tnf/pkg/pacemaker/consolenotification.go Replace hardcoded docsBasePath with docsURLFormat + docsBaseURL() method that reads ClusterVersion
pkg/tnf/operator/starter.go Thread ClusterVersionInformer through HandleDualReplicaClustersrunPacemakerControllers
pkg/operator/starter.go Pass existing clusterVersions informer to HandleDualReplicaClusters
pkg/tnf/pkg/pacemaker/consolenotification_test.go Add TestDocsBaseURL (version extraction, nightly, fallback), update existing tests

Test plan

  • go build ./... passes
  • go test ./pkg/tnf/pkg/pacemaker/ — all 22 tests pass
  • New TestDocsBaseURL covers: full version (4.23.0/4.23/), nightly (4.24.0-0.nightly-.../4.24/), empty ClusterVersion (→ /latest/)
  • Deploy on cluster and verify console notification banner links to correct version docs

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Enhancements
    • Console notifications now include documentation links tailored to the installed OpenShift version.
    • Links automatically fall back to the latest documentation when the installed version is unavailable or cannot be determined.
    • Notification links use category-specific documentation paths and link text.
    • Documentation links now reflect the detected OpenShift minor release for more relevant guidance.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 12, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 12, 2026

Copy link
Copy Markdown

@lucaconsalvi: This pull request references OCPEDGE-2916 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

  • The docsBasePath constant in consolenotification.go was hardcoded to 4.22, so console notification banners (degraded recovery, troubleshooting) always linked to 4.22 docs regardless of the actual cluster version
  • Derives the docs URL version dynamically from ClusterVersion.Status.History[0].Version at runtime, with a "latest" fallback when ClusterVersion is unavailable
  • Follows the same pattern used by MCO (pkg/operator/status.go) introduced by @djoshy in 52ce5d6ec

Changes

File Change
pkg/tnf/pkg/pacemaker/consolenotification.go Replace hardcoded docsBasePath with docsURLFormat + docsBaseURL() method that reads ClusterVersion
pkg/tnf/operator/starter.go Thread ClusterVersionInformer through HandleDualReplicaClustersrunPacemakerControllers
pkg/operator/starter.go Pass existing clusterVersions informer to HandleDualReplicaClusters
pkg/tnf/pkg/pacemaker/consolenotification_test.go Add TestDocsBaseURL (version extraction, nightly, fallback), update existing tests

Test plan

  • go build ./... passes
  • go test ./pkg/tnf/pkg/pacemaker/ — all 22 tests pass
  • New TestDocsBaseURL covers: full version (4.23.0/4.23/), nightly (4.24.0-0.nightly-.../4.24/), empty ClusterVersion (→ /latest/)
  • Deploy on cluster and verify console notification banner links to correct version docs

🤖 Generated with Claude Code

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

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: bbb34a04-7bf6-4787-bb43-23afe6d9cf89

📥 Commits

Reviewing files that changed from the base of the PR and between 2c29d45 and 1d7f300.

📒 Files selected for processing (1)
  • pkg/tnf/operator/starter.go
🚧 Files skipped from review as they are similar to previous changes (1)
  • pkg/tnf/operator/starter.go

Walkthrough

Pacemaker startup now supplies a ClusterVersion lister to the console notification controller. The controller derives versioned documentation URLs, falls back to latest, and appends category-specific fragments. Tests cover version parsing, fallback behavior, and generated notification links.

Changes

Console documentation URL resolution

Layer / File(s) Summary
Notification URL resolution
pkg/tnf/pkg/pacemaker/consolenotification.go
The controller derives a major.minor documentation URL from ClusterVersion history, falls back to latest, and appends category fragments to notification links.
ClusterVersion informer startup
pkg/tnf/operator/starter.go
Pacemaker startup creates and starts the config informer factory, waits for cache synchronization, obtains the ClusterVersion lister, and passes it to the notification controller.
Documentation URL validation
pkg/tnf/pkg/pacemaker/consolenotification_test.go
Tests cover stable and nightly versions, unavailable version data, generated paths and fragments, link text, and updated controller setup.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Mergeability Score: ⚪ Minimal · up to 1d7f3

The version-derived documentation URL change is localized and covered by targeted tests; no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: fonta-rh, tjungblu

Sequence Diagram(s)

sequenceDiagram
  participant PacemakerStartup
  participant ConfigInformerFactory
  participant ConsoleNotificationController
  participant ClusterVersionLister
  participant NotificationResource

  PacemakerStartup->>ConfigInformerFactory: create and start
  ConfigInformerFactory-->>PacemakerStartup: synchronize ClusterVersion cache
  PacemakerStartup->>ConsoleNotificationController: pass ClusterVersion lister
  ConsoleNotificationController->>ClusterVersionLister: read version history
  ClusterVersionLister-->>ConsoleNotificationController: return version or no data
  ConsoleNotificationController->>NotificationResource: provide versioned URL and category fragment
Loading
🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 27.27% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (14 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The changed Go tests use static function and t.Run names. The nightly date appears only in fixture data, not in any test title, and no Ginkgo titles were added.
Test Structure And Quality ✅ Passed The changed tests use Go testing/testify, not Ginkgo. They use only fake clients and indexers, with no cluster resources or Eventually/Consistently waits; this Ginkgo-specific check is inapplicable.
Microshift Test Compatibility ✅ Passed The PR adds only standard Go Test... unit tests; the diff contains no Ginkgo e2e tests, so the MicroShift API compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR adds only standard Go tests with *testing.T; it adds no Ginkgo e2e tests, so the SNO multi-node assumption check does not apply.
Topology-Aware Scheduling Compatibility ✅ Passed The diff only adds ClusterVersion informer/lister wiring and dynamic console URLs; it introduces no affinity, spread, replica, nodeSelector, toleration, or PDB scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The diff adds no stdout writes; OTE main imports only test/e2e, while changed controller packages are not OTE suite setup or imported by that dependency path.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The PR changes only Go unit tests using testing.T; no new Ginkgo e2e tests, IPv6-sensitive URLs, or external connectivity are introduced.
No-Weak-Crypto ✅ Passed The PR changes only OpenShift lister wiring and documentation URL construction; no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, custom crypto, or secret comparisons are introduced.
Container-Privileges ✅ Passed The PR changes only Go source and tests. No container or Kubernetes manifest changed, and no privilege-bearing manifest was modified.
No-Sensitive-Data-In-Logs ✅ Passed The diff adds only two logs. They report client-construction errors and ClusterVersion lister errors; no passwords, tokens, PII, hostnames, or customer data are logged.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: deriving console notification documentation URLs from the cluster version.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci
openshift-ci Bot requested review from fonta-rh and tjungblu August 12, 2026 08:48

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@pkg/tnf/pkg/pacemaker/consolenotification_test.go`:
- Around line 115-125: Update fakeClusterVersionLister to handle the error
returned by indexer.Add when adding the ClusterVersion fixture. Make the test
fixture fail immediately if the add operation fails, using the test failure
mechanism available to the surrounding test context rather than discarding the
error.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 259da7ff-bca4-4321-bb96-9fc8851391e1

📥 Commits

Reviewing files that changed from the base of the PR and between 2849e77 and a2e4569.

📒 Files selected for processing (4)
  • pkg/operator/starter.go
  • pkg/tnf/operator/starter.go
  • pkg/tnf/pkg/pacemaker/consolenotification.go
  • pkg/tnf/pkg/pacemaker/consolenotification_test.go

Comment thread pkg/tnf/pkg/pacemaker/consolenotification_test.go Outdated
@lucaconsalvi

Copy link
Copy Markdown
Contributor Author

/retest

@lucaconsalvi
lucaconsalvi force-pushed the fix/ocpedge-2916-console-docs-link branch from ca5d51d to 2c29d45 Compare August 13, 2026 08:11
Replace the hardcoded OCP 4.22 docs URL in console notifications with
a dynamic version derived from ClusterVersion.Status.History[0].Version,
falling back to "latest" when unavailable. Follows the MCO pattern.

The config client and ClusterVersion informer are created locally in
runPacemakerControllers to keep changes within pkg/tnf/.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@lucaconsalvi
lucaconsalvi force-pushed the fix/ocpedge-2916-console-docs-link branch from 2c29d45 to 1d7f300 Compare August 13, 2026 08:14
@lucaconsalvi

Copy link
Copy Markdown
Contributor Author

Test Results

Tested on a cluster-bot TNF cluster running 5.0.0-0-nightly.

Dynamic version extraction: ClusterVersion 5.0.0-0-2026-08-13-... → extracted 5.0 as major.minor.

Console notification verified: Triggered a degraded state via pcs node maintenance master-0. The red banner appeared in the OpenShift console with the "Recovery guide" link pointing to:

https://docs.redhat.com/en/documentation/openshift_container_platform/5.0/html/.../two-node-with-fencing#operating-a-degraded-tnf

Docs URL validation (in browser):

Version Status
/4.22/ (previously hardcoded) Works
/latest/ (fallback) Works
/5.0/ (pre-release nightly) 404 as expected — docs not published yet

Cleanup: After removing maintenance (pcs node unmaintenance), the notification was automatically cleaned up.

@fonta-rh fonta-rh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nice fix!

@openshift-ci

openshift-ci Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fonta-rh

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

@fonta-rh

Copy link
Copy Markdown
Contributor

/hold
Giving Doug a change to review

@openshift-ci openshift-ci Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Aug 13, 2026
@fonta-rh

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 13, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-agnostic-ovn
/test e2e-agnostic-ovn-upgrade
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-aws-ovn-single-node
/test e2e-gcp-operator
/test e2e-gcp-operator-disruptive
/test e2e-metal-ipi-ovn-ipv6
/test e2e-operator

@dhensel-rh

Copy link
Copy Markdown

/lgtm

@lucaconsalvi

Copy link
Copy Markdown
Contributor Author

verified by @lucaconsalvi

@lucaconsalvi

Copy link
Copy Markdown
Contributor Author

/retest

@lucaconsalvi

Copy link
Copy Markdown
Contributor Author

/retest

@lucaconsalvi

Copy link
Copy Markdown
Contributor Author

/retest

@lucaconsalvi lucaconsalvi changed the title OCPEDGE-2916: Derive console notification docs URL from cluster version OCPBUGS-109743: Derive console notification docs URL from cluster version Aug 14, 2026
@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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 14, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@lucaconsalvi: This pull request references Jira Issue OCPBUGS-109743, which is invalid:

  • expected the bug to target either version "5.1.0." or "openshift-5.1.0.", but it targets "5.0" instead

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:

Summary

  • The docsBasePath constant in consolenotification.go was hardcoded to 4.22, so console notification banners (degraded recovery, troubleshooting) always linked to 4.22 docs regardless of the actual cluster version
  • Derives the docs URL version dynamically from ClusterVersion.Status.History[0].Version at runtime, with a "latest" fallback when ClusterVersion is unavailable
  • Follows the same pattern used by MCO (pkg/operator/status.go)

Changes

File Change
pkg/tnf/pkg/pacemaker/consolenotification.go Replace hardcoded docsBasePath with docsURLFormat + docsBaseURL() method that reads ClusterVersion
pkg/tnf/operator/starter.go Thread ClusterVersionInformer through HandleDualReplicaClustersrunPacemakerControllers
pkg/operator/starter.go Pass existing clusterVersions informer to HandleDualReplicaClusters
pkg/tnf/pkg/pacemaker/consolenotification_test.go Add TestDocsBaseURL (version extraction, nightly, fallback), update existing tests

Test plan

  • go build ./... passes
  • go test ./pkg/tnf/pkg/pacemaker/ — all 22 tests pass
  • New TestDocsBaseURL covers: full version (4.23.0/4.23/), nightly (4.24.0-0.nightly-.../4.24/), empty ClusterVersion (→ /latest/)
  • Deploy on cluster and verify console notification banner links to correct version docs

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Enhancements
  • Console notifications now include documentation links tailored to the installed OpenShift version.
  • Links automatically fall back to the latest documentation when the installed version is unavailable or cannot be determined.
  • Notification links use category-specific documentation paths and link text.
  • Documentation links now reflect the detected OpenShift minor release for more relevant guidance.

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 commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

@lucaconsalvi: 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-ci-robot

Copy link
Copy Markdown

@dhensel-rh: The /verified command must be used with one of the following actions: by, later, remove, or bypass. See https://docs.ci.openshift.org/docs/architecture/jira/#premerge-verification for more information.

Details

In response to this:

/verified

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.

@dhensel-rh

Copy link
Copy Markdown

/verified by @dhensel-rh

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

Copy link
Copy Markdown

@dhensel-rh: This PR has been marked as verified by @dhensel-rh.

Details

In response to this:

/verified by @dhensel-rh

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.

@lucaconsalvi

Copy link
Copy Markdown
Contributor 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 Aug 17, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@lucaconsalvi: This pull request references Jira Issue OCPBUGS-109743, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.1.0) matches configured target version for branch (5.1.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
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.

@lucaconsalvi

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-5.0

@openshift-cherrypick-robot

Copy link
Copy Markdown

@lucaconsalvi: once the present PR merges, I will cherry-pick it on top of release-5.0 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-5.0

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.

@lucaconsalvi

Copy link
Copy Markdown
Contributor Author

/unhold

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 17, 2026
@openshift-merge-bot
openshift-merge-bot Bot merged commit 6b88b76 into openshift:main Aug 17, 2026
18 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@lucaconsalvi: Jira Issue Verification Checks: Jira Issue OCPBUGS-109743
✔️ 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-109743 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:

Summary

  • The docsBasePath constant in consolenotification.go was hardcoded to 4.22, so console notification banners (degraded recovery, troubleshooting) always linked to 4.22 docs regardless of the actual cluster version
  • Derives the docs URL version dynamically from ClusterVersion.Status.History[0].Version at runtime, with a "latest" fallback when ClusterVersion is unavailable
  • Follows the same pattern used by MCO (pkg/operator/status.go)

Changes

File Change
pkg/tnf/pkg/pacemaker/consolenotification.go Replace hardcoded docsBasePath with docsURLFormat + docsBaseURL() method that reads ClusterVersion
pkg/tnf/operator/starter.go Thread ClusterVersionInformer through HandleDualReplicaClustersrunPacemakerControllers
pkg/operator/starter.go Pass existing clusterVersions informer to HandleDualReplicaClusters
pkg/tnf/pkg/pacemaker/consolenotification_test.go Add TestDocsBaseURL (version extraction, nightly, fallback), update existing tests

Test plan

  • go build ./... passes
  • go test ./pkg/tnf/pkg/pacemaker/ — all 22 tests pass
  • New TestDocsBaseURL covers: full version (4.23.0/4.23/), nightly (4.24.0-0.nightly-.../4.24/), empty ClusterVersion (→ /latest/)
  • Deploy on cluster and verify console notification banner links to correct version docs

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Enhancements
  • Console notifications now include documentation links tailored to the installed OpenShift version.
  • Links automatically fall back to the latest documentation when the installed version is unavailable or cannot be determined.
  • Notification links use category-specific documentation paths and link text.
  • Documentation links now reflect the detected OpenShift minor release for more relevant guidance.

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-cherrypick-robot

Copy link
Copy Markdown

@lucaconsalvi: new pull request created: #1679

Details

In response to this:

/cherry-pick release-5.0

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.

@openshift-merge-robot

Copy link
Copy Markdown
Contributor

Fix included in release 5.1.0-0.nightly-2026-08-17-205440

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. 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