Skip to content

Conversation

@lsm5
Copy link
Member

@lsm5 lsm5 commented Jun 7, 2025

Does this PR introduce a user-facing change?

None

This reverts commit 64aaa45.

Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
@openshift-ci openshift-ci bot added release-note-none do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Jun 7, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5

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 Jun 7, 2025
@lsm5 lsm5 force-pushed the v5.4-rhel-tmt-2 branch from 81752cc to 652496c Compare June 7, 2025 18:22
@packit-as-a-service
Copy link

Packit jobs failed. @containers/packit-build please check.

@lsm5 lsm5 force-pushed the v5.4-rhel-tmt-2 branch 2 times, most recently from 855781a to b880038 Compare June 7, 2025 23:08
@lsm5 lsm5 changed the title [IGNORE] [v5.4-rhel] TMT [skip-ci] [IGNORE] [v5.4-rhel] TMT system tests on RHEL Jun 8, 2025
@lsm5 lsm5 force-pushed the v5.4-rhel-tmt-2 branch 3 times, most recently from 6ac3159 to b872198 Compare June 8, 2025 01:35
Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
@lsm5 lsm5 force-pushed the v5.4-rhel-tmt-2 branch from b872198 to 6cc08c4 Compare June 8, 2025 11:43
@lsm5 lsm5 closed this Jun 8, 2025
@lsm5 lsm5 deleted the v5.4-rhel-tmt-2 branch June 8, 2025 22:00
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 7, 2025
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Sep 7, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note-none

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant