chore: Remove explicit VerbosePreference setting, default to SilentlyContinue

[z-Fng]

Motivation and Context

Most Verbose outputs are unnecessary at the moment. Setting VerbosePreference to SilentlyContinue can suppress these outputs.

Relates to:

• Add configuration items to reduce a large amount of meaningless verbose output #66
• feat: Allow configuring PowerShell preference variables #67

Summary by CodeRabbit

• Chores
  • Reduced verbose output during action execution to produce cleaner logs and a smoother user experience.
  • Maintained error handling behavior while removing the explicit verbose setting to rely on default or external logging controls.

[coderabbitai]

Walkthrough

Removed the single assignment that set $Global:VerbosePreference in action.ps1; the script no longer explicitly configures the global verbose preference.

Changes

Global Verbose Preference

Layer / File(s)	Summary
Remove global verbose assignment action.ps1	Deleted the line assigning $Global:VerbosePreference = 'Continue'; no other changes to global preference handling.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I’m a rabbit in the shell so spry,
I hopped through lines and said goodbye.
The noisy logs I now unbind,
A quieter trail is what I find.
🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title accurately reflects the main change: removing the explicit VerbosePreference setting to allow PowerShell to default to SilentlyContinue.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[z-Fng]

It's been nearly six months since PR #67 was completed. I've simplified the changes and resubmitted a new pull request. I was wondering if it would be possible to merge this pull request? Or are there any thoughs on whether this pull request should be merged?