openshift-docs
openshift-docs copied to clipboard
openshift
RHDEVDOCS-6415: Content creation for Pipelines 1.19 RN
Version(s):
none for cherry-picking
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6415
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
QE review:
- [ ] QE has approved this change.
Additional information:
Please do not merge this PR as the release date is scheduled for next week.
@Dhruv-Soni11: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
Issue:
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.
🤖 Thu Jul 03 06:54:04 - Prow CI generated the docs preview: https://94698--ocpdocs-pr.netlify.app Complete list of updated preview URLs: artifacts/updated_preview_urls.txt
@Dhruv-Soni11: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
Issue:
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
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.
🤖 Tue Jun 17 07:25:17 - Prow CI generated the docs preview: https://94698--ocpdocs-pr.netlify.app Complete list of updated preview URLs: artifacts/updated_preview_urls.txt
@Dhruv-Soni11: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
none for cherry-picking
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6415
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
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.
@Dhruv-Soni11: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
none for cherry-picking
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6415
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
QE review:
- [ ] QE has approved this change.
Additional information:
Note to merge-reviewer: As this PR is in a merge-ready state but cannot be merged due to the lack of Errata information, I request you to perform the merge-review normally as you do. This PR will be released sometime during the next week.
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: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
none for cherry-picking
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6415
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
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.
@Dhruv-Soni11: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
none for cherry-picking
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6415
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
QE review:
- [x] 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.
@Dhruv-Soni11: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
none for cherry-picking
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6415
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
QE review:
- [x] QE has approved this change.
Additional information:
Please do not merge this PR as the release date is scheduled for next week.
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.
Hey @Dhruv-Soni11 please get the PR fully ready for merge prior to review.
@Dhruv-Soni11: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
none for cherry-picking
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6415
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
QE review:
- [ ] QE has approved this change.
Additional information:
Please do not merge this PR as the release date is scheduled for next week.
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: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
none for cherry-picking
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6415
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
QE review:
- [x] QE has approved this change.
Additional information:
Please do not merge this PR as the release date is scheduled for next week.
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: 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[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@Dhruv-Soni11: As a reminder, when you put a PR in the merge review queue that you aren't ready to merge yet, please be sure to follow all the steps in the docs manual: https://docs.google.com/document/u/2/d/e/2PACX-1vRLKWEMHQ3DZroxZKfTu3XcrSdREr6D3oSSayBanEprXhkA2Ciyr2SQuDTYI4aIKUiOPPIQMHgjHeh8/pub#h.x8ydklaezdcq
Most importantly, you need to label the PR as a draft or prefix the PR with [WIP]. This step is important because it keeps the PR from being merged accidentally.
/label merge-review-in-progress
@Dhruv-Soni11: This pull request references RHDEVDOCS-6415 which is a valid jira issue.
In response to this:
Version(s):
none for cherry-picking
Issue:
https://issues.redhat.com/browse/RHDEVDOCS-6415
Link to docs preview:
Release notes for Red Hat OpenShift Pipelines General Availability 1.19
QE review:
- [x] 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.
@Dhruv-Soni11: As a reminder, when you put a PR in the merge review queue, please be sure to follow all the steps in the docs manual: https://docs.google.com/document/u/2/d/e/2PACX-1vRLKWEMHQ3DZroxZKfTu3XcrSdREr6D3oSSayBanEprXhkA2Ciyr2SQuDTYI4aIKUiOPPIQMHgjHeh8/pub#h.x8ydklaezdcq
Most importantly, you need to label the PR as a draft or prefix the PR with
[WIP]. This step is important because it keeps the PR from being merged accidentally./label merge-review-in-progress
Hi @michaelryanpeter - Thanks for the reminder about the process. I just realised that I have not removed the note from the Additional Resources section. Just an FYI, I have talked to the team and they have confirmed that the release notes can be merged but not published since this branch is a different one from the main branch used in pipelines. Sorry for any confusion.
Sorry, so this PR can be merged to pipelines-docs-1.19?
I am not involved in the publishing of the pipelines documentation, I think that is handled by your docs team.
I'm sorry, but I am not sure if this is ready for a merge or a merge review, since your last comment mentioned needing to take something out of the additional resources section.
I am going to take off the merge review in progress label and merge review needed label too. I am sorry if I did this in error.
When you are ready for this to be merged, please remove the [WIP] prefix (which I added because I thought you needed it) from the PR and add it back into the queue.
cc: @kalexand-rh /remove-label merge-review-in-progress /remove-label merge-review-needed
I'm sorry, but I am not sure if this is ready for a merge or a merge review, since your last comment mentioned needing to take something out of the additional resources section.
I am going to take off the merge review in progress label and merge review needed label too. I am sorry if I did this in error.
When you are ready for this to be merged, please remove the
[WIP]prefix (which I added because I thought you needed it) from the PR and add it back into the queue.cc: @kalexand-rh /remove-label merge-review-in-progress /remove-label merge-review-needed
Hi @michaelryanpeter - This PR is ready for a merge review, and I will remove the label you added from this PR. Sorry for any confusion.
@Dhruv-Soni11 It was a long week on peer review. There is a pretty good chance that I got myself confused! Take care!