Skip to content

<do-not-merge> RHDEVDOCS-6444: Content creation for GitOps 1.15.2 #92626

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

Draft
wants to merge 1 commit into
base: gitops-docs-1.15
Choose a base branch
from

Conversation

Dhruv-Soni11
Copy link
Contributor

@Dhruv-Soni11 Dhruv-Soni11 commented Apr 25, 2025

Version(s):

gitops-docs-1.15, gitops-docs-1.16, gitops-docs-main

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6444

Link to docs preview:

Release Notes for GitOps v1.15.2

QE review:

  • QE has approved this change.

SME review: @Rizwana777, [email protected], [email protected], [email protected]
QE review: @varshab1210
Peer review: @mburke5678

Additional information:

Kindly perform the merge review as per the normal steps, but do not merge the PR if everything looks fine, as the SME/QE team might provide us with an additional release note.

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

openshift-ci-robot commented Apr 25, 2025

@Dhruv-Soni11: This pull request references RHDEVDOCS-6444 which is a valid jira issue.

In response to this:

Version(s):

GitOps 1.15, GitOps 1.16

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6444

Link to docs preview:

QE review:

  • QE has approved this change.

SME review:
QE review:
Peer review:

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/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 25, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Apr 25, 2025

@Dhruv-Soni11
Copy link
Contributor Author

/retest

@Dhruv-Soni11 Dhruv-Soni11 force-pushed the RHDEVDOCS-6444 branch 2 times, most recently from db334e1 to 5b57240 Compare April 28, 2025 10:58
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 28, 2025

@Dhruv-Soni11: This pull request references RHDEVDOCS-6444 which is a valid jira issue.

In response to this:

Version(s):

GitOps 1.15, GitOps 1.16

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6444

Link to docs preview:

Release Notes for GitOps v1.15.2

QE review:

  • QE has approved this change.

SME review: @Rizwana777, [email protected], [email protected], [email protected]
QE review:
Peer review:

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-robot
Copy link

openshift-ci-robot commented Apr 28, 2025

@Dhruv-Soni11: This pull request references RHDEVDOCS-6444 which is a valid jira issue.

In response to this:

Version(s):

GitOps 1.15, GitOps 1.16

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6444

Link to docs preview:

Release Notes for GitOps v1.15.2

QE review:

  • QE has approved this change.

SME review: @Rizwana777, [email protected], [email protected], [email protected]
QE review: @varshab1210
Peer review:

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.

@Dhruv-Soni11
Copy link
Contributor Author

/retest

@varshab1210
Copy link

@Dhruv-Soni11 please add RN from https://issues.redhat.com/browse/GITOPS-6150 once its available

@Rizwana777
Copy link

@Dhruv-Soni11 please add RN from https://issues.redhat.com/browse/GITOPS-6150 once its available

https://issues.redhat.com/browse/GITOPS-6150 RN is available, you can add it @Dhruv-Soni11, apologies, I missed mentioning this ticket before, and thanks Varsha for pointing out

@varshab1210
Copy link

LGTM, thanks

Copy link

@aali309 aali309 left a comment

Choose a reason for hiding this comment

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

LGTM!

@Dhruv-Soni11
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 May 7, 2025
@mburke5678 mburke5678 added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label May 7, 2025
@mburke5678
Copy link
Contributor

@Dhruv-Soni11 A few comments. Otherwise LGTM

@mburke5678 mburke5678 added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR peer-review-needed Signifies that the peer review team needs to review this PR labels May 7, 2025
@Dhruv-Soni11 Dhruv-Soni11 force-pushed the RHDEVDOCS-6444 branch 3 times, most recently from 3b775b0 to 52f77be Compare May 8, 2025 13:08
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 9, 2025
@Dhruv-Soni11 Dhruv-Soni11 changed the title RHDEVDOCS-6444: Content creation for GitOps 1.15.2 <do-not-merge> RHDEVDOCS-6444: Content creation for GitOps 1.15.2 May 9, 2025
@Dhruv-Soni11
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 May 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 9, 2025

@Dhruv-Soni11: This pull request references RHDEVDOCS-6444 which is a valid jira issue.

In response to this:

Version(s):

GitOps 1.15, GitOps 1.16

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6444

Link to docs preview:

Release Notes for GitOps v1.15.2

QE review:

  • QE has approved this change.

SME review: @Rizwana777, [email protected], [email protected], [email protected]
QE review: @varshab1210
Peer review:

Additional information:

Kindly perform the merge review as per the normal steps, but do not merge the PR if everything looks fine, as the SME/QE team has not provided us with the Errata doc 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented May 9, 2025

@Dhruv-Soni11: This pull request references RHDEVDOCS-6444 which is a valid jira issue.

In response to this:

Version(s):

GitOps 1.15, GitOps 1.16

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6444

Link to docs preview:

Release Notes for GitOps v1.15.2

QE review:

  • QE has approved this change.

SME review: @Rizwana777, [email protected], [email protected], [email protected]
QE review: @varshab1210
Peer review: @mburke5678

Additional information:

Kindly perform the merge review as per the normal steps, but do not merge the PR if everything looks fine, as the SME/QE team has not provided us with the Errata doc 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 openshift-eng/jira-lifecycle-plugin repository.

@mburke5678 mburke5678 added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label May 9, 2025
@mburke5678
Copy link
Contributor

@Dhruv-Soni11 Had a couple of comments before merge. Probably wouldn't have held up the merge over these issues. But, where we are not merging yet, maybe you could take a look. When it comes time to merge, let me know and we can avoid wasting the time of another merge reviewer over these two issues.

@mburke5678 mburke5678 removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels May 9, 2025
@Dhruv-Soni11
Copy link
Contributor Author

Dhruv-Soni11 commented May 12, 2025

@Dhruv-Soni11 Had a couple of comments before merge. Probably wouldn't have held up the merge over these issues. But, where we are not merging yet, maybe you could take a look. When it comes time to merge, let me know and we can avoid wasting the time of another merge reviewer over these two issues.

Thanks for performing a quick merge review on this PR, @mburke5678. I have fixed a couple of your comments and am waiting for further instructions from the QE and SME team to add the errata details. Once I get those details, I will update this PR and tag you for merge review. Thanks for the quick comments and suggestions.

Fixed QE review comments

Incorporating SME review comments
@Dhruv-Soni11 Dhruv-Soni11 marked this pull request as ready for review May 16, 2025 06:51
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 16, 2025
@Dhruv-Soni11 Dhruv-Soni11 changed the title <do-not-merge> RHDEVDOCS-6444: Content creation for GitOps 1.15.2 RHDEVDOCS-6444: Content creation for GitOps 1.15.2 May 16, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 16, 2025

@Dhruv-Soni11: This pull request references RHDEVDOCS-6444 which is a valid jira issue.

In response to this:

Version(s):

GitOps 1.15, GitOps 1.16

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6444

Link to docs preview:

Release Notes for GitOps v1.15.2

QE review:

  • QE has approved this change.

SME review: @Rizwana777, [email protected], [email protected], [email protected]
QE review: @varshab1210
Peer review: @mburke5678

Additional information:

Kindly perform the merge review as per the normal steps, but do not merge the PR if everything looks fine, as the SME/QE team has not provided us with the Errata doc 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label May 16, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 16, 2025

@Dhruv-Soni11: This pull request references RHDEVDOCS-6444 which is a valid jira issue.

In response to this:

Version(s):

gitops-docs-1.15, gitops-docs-1.16, gitops-docs-main

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6444

Link to docs preview:

Release Notes for GitOps v1.15.2

QE review:

  • QE has approved this change.

SME review: @Rizwana777, [email protected], [email protected], [email protected]
QE review: @varshab1210
Peer review: @mburke5678

Additional information:

Kindly perform the merge review as per the normal steps, but do not merge the PR if everything looks fine, as the SME/QE team has not provided us with the Errata doc 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 openshift-eng/jira-lifecycle-plugin repository.

Copy link

openshift-ci bot commented May 16, 2025

@Dhruv-Soni11: 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.

@Dhruv-Soni11 Dhruv-Soni11 marked this pull request as draft May 16, 2025 10:28
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 16, 2025
@Dhruv-Soni11 Dhruv-Soni11 changed the title RHDEVDOCS-6444: Content creation for GitOps 1.15.2 <do-not-merge> RHDEVDOCS-6444: Content creation for GitOps 1.15.2 May 16, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 16, 2025

@Dhruv-Soni11: This pull request references RHDEVDOCS-6444 which is a valid jira issue.

In response to this:

Version(s):

gitops-docs-1.15, gitops-docs-1.16, gitops-docs-main

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6444

Link to docs preview:

Release Notes for GitOps v1.15.2

QE review:

  • QE has approved this change.

SME review: @Rizwana777, [email protected], [email protected], [email protected]
QE review: @varshab1210
Peer review: @mburke5678

Additional information:

Kindly perform the merge review as per the normal steps, but do not merge the PR if everything looks fine, as the SME/QE team might provide us with an additional release note.

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.

@sheriff-rh sheriff-rh added merge-review-in-progress Signifies that the merge review team is reviewing this PR ok-to-merge and removed merge-review-needed Signifies that the merge review team needs to review this PR merge-review-in-progress Signifies that the merge review team is reviewing this PR labels May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-merge peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants