Revert "Update cli-minikit.yml"

[Dargon789]

Reverts #49

Summary by Sourcery

CI:

• Restore the cli-minikit workflow name and CLI invocation to their prior minikit-specific behavior, effectively reverting the earlier onchainkit changes.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Reverts the previous change that adapted the workflow from the minikit CLI to the generic onchainkit CLI, restoring the original minikit-focused workflow configuration and conflict markers that need cleanup.

Flow diagram for restored minikit CLI test workflow steps

flowchart TD
  Start["Start_workflow_on_pull_request"] --> Checkout["Checkout_repository"]
  Checkout --> SetupNode["Setup_Node_js_version"]
  SetupNode --> InstallRootDeps["Install_root_dependencies_with_npm_install"]
  InstallRootDeps --> MkdirTestProject["Create_test_project_directory"]
  MkdirTestProject --> RunCliMinikit["Run_create_onchain_cli_with_mini_flag_and_scripted_input"]
  RunCliMinikit --> CdGeneratedApp["Change_directory_to_my_onchainkit_app"]
  CdGeneratedApp --> InstallAppDeps["Install_app_dependencies_with_npm_install"]
  InstallAppDeps --> BuildApp["Build_app_with_npm_run_build"]
  BuildApp --> End["End_workflow_job"]

Loading

File-Level Changes

Change	Details	Files
Restore workflow name and CLI invocation back to the minikit-specific configuration instead of the generic onchainkit version.	Change workflow name string back from the onchainkit-oriented label to the minikit label. Update the CLI command pipeline to use the --mini flag and original interactive input sequence instead of the generic onchainkit invocation.	.github/workflows/cli-minikit.yml
Introduce merge conflict markers between the current branch and upstream/main workflow variants that must be resolved.	Add Git conflict markers around the workflow name section. Add Git conflict markers around the CLI invocation command block.	.github/workflows/cli-minikit.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sourcery-ai]

Hey - I've left some high level feedback:

• The workflow file still contains Git conflict markers (<<<<<<<<, ========, >>>>>>>>); these need to be resolved so that only the intended version of the job name and CLI invocation remains.
• Given this is a revert, double-check that the selected workflow name (cli: build & install ...) and CLI command (--mini vs no flag) consistently match the state you want to restore, rather than mixing parts of both branches.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The workflow file still contains Git conflict markers (`<<<<<<<<`, `========`, `>>>>>>>>`); these need to be resolved so that only the intended version of the job name and CLI invocation remains.
- Given this is a revert, double-check that the selected workflow name (`cli: build & install ...`) and CLI command (`--mini` vs no flag) consistently match the state you want to restore, rather than mixing parts of both branches.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}