Skip to content

OBSDOCS-2180: Github - Add advisory to release notes #96189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: standalone-logging-docs-6.3
Choose a base branch
from

Conversation

theashiot
Copy link
Contributor

@theashiot theashiot commented Jul 16, 2025

Version(s): 6.3

Issue: https://issues.redhat.com/browse/OBSDOCS-2180

Link to docs preview: https://96189--ocpdocs-pr.netlify.app/openshift-logging/latest/about/logging-release-notes.html#logging-release-notes-6-3-0_logging-release-notes

QE review: Not required as the change does not impact the meaning of the docs.

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 16, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 16, 2025

@theashiot: This pull request references OBSDOCS-2180 which is a valid jira issue.

In response to this:

Version(s): 6.3

Issue: https://issues.redhat.com/browse/OBSDOCS-2180

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 16, 2025
@ocpdocs-previewbot
Copy link

🤖 Wed Jul 16 21:12:28 - Prow CI generated the docs preview:

https://96189--ocpdocs-pr.netlify.app/openshift-logging/latest/about/logging-release-notes.html

Copy link

openshift-ci bot commented Jul 16, 2025

@theashiot: 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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 16, 2025

@theashiot: This pull request references OBSDOCS-2180 which is a valid jira issue.

In response to this:

Version(s): 6.3

Issue: https://issues.redhat.com/browse/OBSDOCS-2180

Link to docs preview: https://96189--ocpdocs-pr.netlify.app/openshift-logging/latest/about/logging-release-notes.html#logging-release-notes-6-3-0_logging-release-notes

QE review: Not required as the change does not impact the meaning of the docs.

Additional information:

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.

@theashiot
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Jul 16, 2025
@abrennan89 abrennan89 added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jul 17, 2025
@abrennan89
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 17, 2025
@theashiot
Copy link
Contributor Author

Thanks, @abrennan89!

@theashiot
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Jul 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. merge-review-needed Signifies that the merge review team needs to review this PR peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants