Skip to content

Conversation

martin-s-a
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot requested review from cajieh and jhadvig February 24, 2025 15:31
@openshift-ci openshift-ci bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. component/core Related to console core functionality labels Feb 24, 2025
Copy link
Contributor

openshift-ci bot commented Feb 24, 2025

Hi @MartinSalinas98. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@openshift-ci openshift-ci bot added the kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated label Feb 24, 2025
@logonoff
Copy link
Member

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 14, 2025
"Create {{label}}": "Crear {{label}}",
"Edit {{label}}": "Editar {{label}}",
"{helpText}": "{helpText}",
"Create PodDiscruptionBudget": "Crear PodDiscruptionBudget",
Copy link
Member

@logonoff logonoff Mar 14, 2025

Choose a reason for hiding this comment

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

were these changes in es, fr, ja, ko, and zh done by hand, or by running yarn i18n?

Copy link
Contributor Author

@martin-s-a martin-s-a Mar 14, 2025

Choose a reason for hiding this comment

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

They were completely manual, since I made them from GitHub's web interface without even cloning the repository.

Copy link
Contributor

Choose a reason for hiding this comment

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

The en locale is updated using yarn i18n, but other supported language locales are updated in the translations portal. For this type of typo error, I suggest you run yarn i18n to update the en locale, and a manual update for other locales is fine, as the word is a resource name which should be in English.
Good catch!

Copy link
Contributor Author

@martin-s-a martin-s-a Mar 15, 2025

Choose a reason for hiding this comment

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

I just tried setting up the project locally and running yarn i18n, but no files seemed to change appart from some package.json files, with apparently unrelated content. So, I guess in this specific case no further changes needed to be applied?

Note: I have basically 0 experience setting up & running openshift locally, so I might make some fairly basic mistakes, thanks for the patience.

@logonoff
Copy link
Member

/retitle NO-JIRA: Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget

@openshift-ci openshift-ci bot changed the title Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget NO-JIRA: Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget Mar 14, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 14, 2025
@openshift-ci-robot
Copy link
Contributor

@MartinSalinas98: This pull request explicitly references no jira issue.

In response to this:

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.

@logonoff
Copy link
Member

/label px-approved
/label docs-approved

@openshift-ci openshift-ci bot added px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Mar 14, 2025
Copy link
Member

@logonoff logonoff left a comment

Choose a reason for hiding this comment

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

/assign cajieh

no qe-approved needed for bugs

/label qe-approved

/lgtm

/label tide/merge-method-squash

@openshift-ci openshift-ci bot added qe-approved Signifies that QE has signed off on this PR tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. labels Mar 17, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 17, 2025
@cajieh
Copy link
Contributor

cajieh commented Mar 20, 2025

/retitle NO-JIRA: Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget

I created a Jira to track this change - Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget. Update the PR title and reassign the ticket accordingly.

@cajieh
Copy link
Contributor

cajieh commented Mar 20, 2025

/lgtm

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 20, 2025
@cajieh
Copy link
Contributor

cajieh commented Mar 20, 2025

/approve

@logonoff
Copy link
Member

logonoff commented Mar 20, 2025

/retitle OCPBUGS-53385: Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget

@openshift-ci openshift-ci bot changed the title NO-JIRA: Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget OCPBUGS-53385Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget Mar 20, 2025
@logonoff
Copy link
Member

/retitle OCPBUGS-53385: Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget

@openshift-ci openshift-ci bot changed the title OCPBUGS-53385Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget OCPBUGS-53385: Fixed typo: PodDiscruptionBudget -> PodDisruptionBudget Mar 20, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 20, 2025
@openshift-ci-robot
Copy link
Contributor

@MartinSalinas98: This pull request references Jira Issue OCPBUGS-53385, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

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 requested a review from yapei March 20, 2025 12:39
@logonoff
Copy link
Member

/remove-label px-approved
/remove-label qe-approved
/remove-label docs-approved

@openshift-ci openshift-ci bot removed px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Mar 20, 2025
@openshift-ci-robot
Copy link
Contributor

@MartinSalinas98: This pull request references Jira Issue OCPBUGS-53385, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

In response to this:

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
Contributor

/retest-required

Remaining retests: 0 against base HEAD e305329 and 2 for PR HEAD ec88a04 in total

2 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD e305329 and 2 for PR HEAD ec88a04 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD e305329 and 2 for PR HEAD ec88a04 in total

@logonoff
Copy link
Member

/label acknowledge-critical-fixes-only
/lgtm

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Mar 23, 2025
Copy link
Contributor

openshift-ci bot commented Mar 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cajieh, logonoff, MartinSalinas98

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

/retest-required

Remaining retests: 0 against base HEAD 9d52220 and 1 for PR HEAD ec88a04 in total

Copy link
Contributor

openshift-ci bot commented Mar 23, 2025

@MartinSalinas98: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn ec88a04 link false /test okd-scos-e2e-aws-ovn

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
Contributor

/retest-required

Remaining retests: 0 against base HEAD bf0a952 and 0 for PR HEAD ec88a04 in total

@openshift-merge-bot openshift-merge-bot bot merged commit d89cabe into openshift:main Mar 23, 2025
7 of 8 checks passed
@openshift-ci-robot
Copy link
Contributor

@MartinSalinas98: Jira Issue OCPBUGS-53385: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-53385 has been moved to the MODIFIED state.

In response to this:

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.

krishagarwal278 pushed a commit to krishagarwal278/console that referenced this pull request Jun 30, 2025
openshift-merge-bot bot pushed a commit that referenced this pull request Jul 3, 2025
Co-authored-by: Martin Salinas <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. component/core Related to console core functionality jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/i18n Indicates issue or PR relates to internationalization or has content that needs to be translated lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants