Skip to content
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.

Sign up for GitHub

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

Jump to bottom

OPCT-200: rename to opct on codebase #131

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

OPCT-200: rename to opct on codebase #131

wants to merge 1 commit into from

Conversation

mtulio
Copy link
Contributor

@mtulio mtulio commented Dec 28, 2024 •
edited
Loading

Rename remaining statements referencing the old name of project.

https://issues.redhat.com/browse/OPCT-200

@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 Dec 28, 2024
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Dec 28, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from mtulio. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@mtulio mtulio changed the title OPCT-000: rename to opct from codebase OPCT-311: rename to opct from codebase Dec 28, 2024
@mtulio mtulio changed the title OPCT-311: rename to opct from codebase OPCT-200: rename to opct from codebase Dec 28, 2024
@mtulio mtulio changed the title OPCT-200: rename to opct from codebase OPCT-200: rename to opct on codebase Dec 28, 2024
@mtulio mtulio added target-release/opct-v0.5 target-release/opct-v0.6 priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed target-release/opct-v0.5 target-release/opct-v0.6 labels Dec 28, 2024
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. target-release/opct-v0.5
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@mtulio @openshift-merge-robot