remove unused methods

[motatoes]

Summary by CodeRabbit

• Refactor
  • Streamlined CLI operations by removing outdated command execution and reporting functionalities. These updates simplify internal processing for a leaner, more maintainable codebase without altering the overall user experience.

[coderabbitai]

Walkthrough

The changes remove several components from the main command file. Specifically, multiple import statements related to various digger functionalities have been removed, and three functions—exec, getImpactedProjectsAsString, and logCommands—have been entirely deleted. The deletions simplify the control flow by eliminating command execution, project impact reporting, and logging logic, while the initialization via the init function remains intact.

Changes

File	Change Summary
cli/cmd/digger/main.go	Removed import statements (digger, core_backend, ci, reporting, etc.) and deleted functions: exec, getImpactedProjectsAsString, and logCommands. Init function remains unchanged.

Poem

Oh, I’m a rabbit with a joyful leap,
As code gets lighter, no more to keep.
Imports and functions hop away in flight,
Leaving space for clearer code to shine bright.
With each deletion, my heart sings with delight! 🐰🥕

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7deabf0 and fd30573.

📒 Files selected for processing (1)

• cli/cmd/digger/main.go (0 hunks)

💤 Files with no reviewable changes (1)

• cli/cmd/digger/main.go

⏰ Context from checks skipped due to timeout of 90000ms (10)

• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build
• GitHub Check: Build

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.