Show actual ci-info output

[mernst]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes refactor the ci-info command output handling by introducing an intermediate variable (ci_info_output) to capture the command output before evaluation, replacing the previous direct eval approach. Additional debug logging statements are incorporated to print the captured output and mark when evaluation occurs. Debug messages surrounding this operation are adjusted accordingly. The core logic remains unchanged; only the execution method and timing are modified. The alterations add 12 lines and remove 2 lines of code.

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 87938a2 and a9b7341.

📒 Files selected for processing (1)

• git-clone-related

🔇 Additional comments (1)

git-clone-related (1)

134-147: LGTM! Good refactoring for improved debuggability.

Capturing the output in an intermediate variable before eval is a sensible approach that enables visibility into what's being executed. The debug logging with clear start/end markers will help troubleshoot CI issues.

One minor observation: if ci-info fails, ci_info_output may be empty or contain an error message. While this is pre-existing behavior (the original code also didn't check for failures), you might consider adding a check like:

if [ -z "${ci_info_output}" ]; then
  echo "${SCRIPT_NAME}: ci-info returned empty output" >&2
  exit 1
fi

This is optional given the existing error tolerance pattern (set +e).

---

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.}