Skip to content

OTA-2069: Update approval disclaimer to irreversibility language - #18

Open
ankitathomas wants to merge 1 commit into
openshift:mainfrom
ankitathomas:text-update
Open

OTA-2069: Update approval disclaimer to irreversibility language#18
ankitathomas wants to merge 1 commit into
openshift:mainfrom
ankitathomas:text-update

Conversation

@ankitathomas

Copy link
Copy Markdown

Update approval disclaimer to irreversibility language

Changes:

  • Update button label from 'Approve & upgrade' to 'Start update'
  • Update confirmation button to 'Confirm and start update'
  • Add disclaimer text: 'OCP updates are irreversible.'
  • Maintain 5-second safety timeout (already implemented)

@openshift-ci-robot

openshift-ci-robot commented Jul 17, 2026

Copy link
Copy Markdown

@ankitathomas: This pull request references OTA-2069 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Update approval disclaimer to irreversibility language

Changes:

  • Update button label from 'Approve & upgrade' to 'Start update'
  • Update confirmation button to 'Confirm and start update'
  • Add disclaimer text: 'OCP updates are irreversible.'
  • Maintain 5-second safety timeout (already implemented)

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 17, 2026
@openshift-ci
openshift-ci Bot requested review from DavidHurta and jhadvig July 17, 2026 12:10
@ankitathomas ankitathomas reopened this Jul 20, 2026
@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 24, 2026
Signed-off-by: Ankita Thomas <ankithom@redhat.com>
Co-Authored-By: Claude <noreply@anthropic.com>
@openshift-ci openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 29, 2026
@openshift-ci

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown

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

@wking wking left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 30, 2026
@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ankitathomas, wking

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 30, 2026
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/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants