Skip to content

Conversation

@ardaguclu
Copy link
Member

@ardaguclu ardaguclu commented Oct 6, 2025

Note: I tried to migrate from archived github.com/gonum/graph to gonum.org/v1/gonum. But it requires some major changes. So I'll defer this for now as a very nice to have in the future.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 6, 2025
@openshift-ci-robot
Copy link

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

@coderabbitai
Copy link

coderabbitai bot commented Oct 6, 2025

Walkthrough

Updated dependencies in go.mod: replaced github.com/alessio/shellescape with al.essio.dev/pkg/shellescape and bumped github.com/alexbrainman/sspi version. Adjusted one Go file to use the new shellescape import path. No functional or API changes indicated.

Changes

Cohort / File(s) Summary
Dependency updates
go.mod
Added al.essio.dev/pkg/shellescape@v1.6.0, removed github.com/alessio/shellescape@v1.4.1, updated github.com/alexbrainman/sspi to v0.0.0-20250919150558-7d374ff0d59e.
Import path migration
pkg/cli/admin/copytonode/copy_to_node.go
Switched import from github.com/alessio/shellescape to al.essio.dev/pkg/shellescape; no code logic changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title Check ✅ Passed The pull request title clearly identifies the primary changes, namely updating the shellescape and sspi dependencies, and does so concisely without extraneous detail.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Description Check ✅ Passed The pull request description explicitly outlines updating the shellescape package path to its new domain and bumping the sspi dependency with a link to the relevant upstream pull request addressing Azure constraints, which directly corresponds to the modifications in go.mod and import statements. It also includes context for potential future work and guidance for related debugging, making it clearly relevant and informative for reviewers. The details align with the raw summary of changes and objectives, confirming that the description accurately captures the scope and intent of the pull request.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 6, 2025
@ardaguclu
Copy link
Member Author

/hold
until reviewed
/cc @tchap
could you PTAL?.

@openshift-ci openshift-ci bot requested a review from tchap October 6, 2025 09:26
@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 6, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between a25e854 and 5bb9e8c.

⛔ Files ignored due to path filters (15)
  • go.sum is excluded by !**/*.sum
  • vendor/al.essio.dev/pkg/shellescape/.gitignore is excluded by !vendor/**, !**/vendor/**
  • vendor/al.essio.dev/pkg/shellescape/.golangci.yml is excluded by !vendor/**, !**/vendor/**
  • vendor/al.essio.dev/pkg/shellescape/.goreleaser.yml is excluded by !vendor/**, !**/vendor/**
  • vendor/al.essio.dev/pkg/shellescape/AUTHORS is excluded by !vendor/**, !**/vendor/**
  • vendor/al.essio.dev/pkg/shellescape/CODE_OF_CONDUCT.md is excluded by !vendor/**, !**/vendor/**
  • vendor/al.essio.dev/pkg/shellescape/LICENSE is excluded by !vendor/**, !**/vendor/**
  • vendor/al.essio.dev/pkg/shellescape/Makefile is excluded by !vendor/**, !**/vendor/**
  • vendor/al.essio.dev/pkg/shellescape/README.md is excluded by !vendor/**, !**/vendor/**
  • vendor/al.essio.dev/pkg/shellescape/shellescape.go is excluded by !vendor/**, !**/vendor/**
  • vendor/github.com/alessio/shellescape/.goreleaser.yml is excluded by !vendor/**, !**/vendor/**
  • vendor/github.com/alessio/shellescape/CODE_OF_CONDUCT.md is excluded by !vendor/**, !**/vendor/**
  • vendor/github.com/alexbrainman/sspi/internal/common/common.go is excluded by !vendor/**, !**/vendor/**
  • vendor/github.com/alexbrainman/sspi/syscall.go is excluded by !vendor/**, !**/vendor/**
  • vendor/modules.txt is excluded by !vendor/**, !**/vendor/**
📒 Files selected for processing (2)
  • go.mod (1 hunks)
  • pkg/cli/admin/copytonode/copy_to_node.go (1 hunks)
🔇 Additional comments (1)
pkg/cli/admin/copytonode/copy_to_node.go (1)

14-14: Import path update to the new module domain is correct

The vanity path switch lines up with the v1.6.0 module and the Quote/QuoteCommand APIs in use remain stable, so no call-site adjustments are needed. Based on learnings

@tchap
Copy link
Contributor

tchap commented Oct 6, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 6, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu, tchap

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

@ardaguclu
Copy link
Member Author

I think, we don't have to verify this manually. If CI is green, we are ok.
/verify bypass

@ardaguclu
Copy link
Member Author

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 6, 2025
@openshift-ci-robot
Copy link

@ardaguclu: The verified label has been added.

In response to this:

/verified bypass

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.

@ardaguclu
Copy link
Member Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 6, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 6632635 into openshift:main Oct 6, 2025
17 of 19 checks passed
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 6, 2025

@ardaguclu: 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 5bb9e8c 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.

@ardaguclu ardaguclu deleted the update-packages branch October 6, 2025 13:35
@Neustradamus
Copy link

@ardaguclu: Thanks for your update!

Linked to:

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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants