openshift-docs
openshift-docs copied to clipboard
TELCODOCS#2164: Added pin information
Version(s): 4.17+
Issue: TELCODOCS-2164
Link to docs preview:
QE review:
- [x] QE has approved this change.
@vitus133 Could you please review this PR? Thanks!
🤖 Mon Jun 30 18:48:53 - Prow CI generated the docs preview:
https://95044--ocpdocs-pr.netlify.app/openshift-enterprise/latest/networking/ptp/configuring-ptp.html
/lgtm
@ajaggapa Could you please review this PR? Thanks!
/label lgtm
@hhassid: The label(s) /label lgtm cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, peer-review-done, peer-review-in-progress, peer-review-needed, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, stability-fix-approved, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?
In response to this:
/label lgtm
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.
@sr1kar99: Those labels are not set on the issue: peer-review-needed
In response to this:
/label peer-review-in-progress /remove-label peer-review-needed
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.
/label peer-review-needed
/remove-label peer-review-in-progress
/label peer-review-in-progress
/remove-label peer-review-in-progress
/remove-label peer-review-needed
/label peer-review-done
@sr1kar99 please wait for my comments to be double checked as I am new to peer review. @agantony please review the comments.
New changes are detected. LGTM label has been removed.
Added a few additional comments; overall lgtm!
Great suggestions! Updated the content. Thank you @agantony @aravipra
@sr1kar99: all tests passed!
Full PR test history. Your PR dashboard.
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.
/label merge-review-needed
/cherry-pick enterprise-4.17
/cherry-pick enterprise-4.18
/cherry-pick enterprise-4.19
/cherry-pick enterprise-4.20
@stevsmit: new pull request created: #95522
In response to this:
/cherry-pick enterprise-4.17
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.
@stevsmit: new pull request created: #95523
In response to this:
/cherry-pick enterprise-4.18
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.
@stevsmit: new pull request created: #95524
In response to this:
/cherry-pick enterprise-4.19
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.
@stevsmit: new pull request created: #95525
In response to this:
/cherry-pick enterprise-4.20
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.