Skip to content

chore: expose flows command#152

Merged
gfyrag merged 1 commit into
mainfrom
chore/expose-flows
May 29, 2026
Merged

chore: expose flows command#152
gfyrag merged 1 commit into
mainfrom
chore/expose-flows

Conversation

@gfyrag

@gfyrag gfyrag commented May 7, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@gfyrag gfyrag requested a review from a team as a code owner May 7, 2026 12:39
@coderabbitai

coderabbitai Bot commented May 7, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f8ba16ae-deb6-4bff-b236-9e34d37f0ec4

📥 Commits

Reviewing files that changed from the base of the PR and between 839e9eb and 6555011.

📒 Files selected for processing (1)
  • cmd/orchestration/root.go
💤 Files with no reviewable changes (1)
  • cmd/orchestration/root.go

Walkthrough

Removes the fctl.WithHidden() option from the orchestration root command constructor, making the command visible in the CLI. No public interfaces or child command wiring are altered.

Changes

Orchestration CLI Visibility

Layer / File(s) Summary
Remove hidden flag from orchestration command
cmd/orchestration/root.go
The NewCommand() function constructs the orchestration root stack command without the fctl.WithHidden() option, changing its visibility in the CLI.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hidden command hops into view,
The orchestration stage gets its debut,
One line removed, no clutter or fuss,
The CLI is cleaner for all of us! 🎭

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive No description was provided by the author, making it impossible to assess whether the description relates to the changeset. Add a pull request description explaining why the orchestration flows command is being exposed and any relevant context for reviewers.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title 'expose flows command' accurately describes the main change: removing the hidden flag from the orchestration command to make it visible/exposed to users.
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.

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

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/expose-flows

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@ledger-v3-poc`:
- Line 1: The repo contains a staged submodule pointer named "ledger-v3-poc"
without a matching .gitmodules entry which will break git clone
--recurse-submodules and git submodule update; either remove the submodule
commit reference or add a proper .gitmodules entry and initialize the submodule.
To fix, delete the staged submodule entry (undo the commit that adds
ledger-v3-poc) if it's unrelated, or create and commit a correct .gitmodules
section referencing ledger-v3-poc with the correct URL and path, run git
submodule sync && git submodule update --init --recursive to verify, and ensure
no code references ledger-v3-poc remain (search for ledger-v3-poc) before
pushing.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8e6b579d-8dd5-425f-80ac-8dbf8cabed26

📥 Commits

Reviewing files that changed from the base of the PR and between 2c531a2 and 839e9eb.

📒 Files selected for processing (2)
  • cmd/orchestration/root.go
  • ledger-v3-poc
💤 Files with no reviewable changes (1)
  • cmd/orchestration/root.go

Comment thread ledger-v3-poc Outdated
@gfyrag gfyrag enabled auto-merge (squash) May 7, 2026 17:14
@flemzord flemzord force-pushed the chore/expose-flows branch from 839e9eb to 6555011 Compare May 29, 2026 08:14
@gfyrag gfyrag merged commit 01fe120 into main May 29, 2026
5 checks passed
@gfyrag gfyrag deleted the chore/expose-flows branch May 29, 2026 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants