Skip to content

fix(minimax-docx): cd to DOTNET_DIR before dotnet restore/build#50

Open
JithendraNara wants to merge 1 commit intoMiniMax-AI:mainfrom
JithendraNara:fix/minimax-docx-frontmatter
Open

fix(minimax-docx): cd to DOTNET_DIR before dotnet restore/build#50
JithendraNara wants to merge 1 commit intoMiniMax-AI:mainfrom
JithendraNara:fix/minimax-docx-frontmatter

Conversation

@JithendraNara
Copy link
Copy Markdown
Contributor

Summary

  • Fix env_check.sh to cd "$DOTNET_DIR" before running dotnet restore and dotnet build
  • This resolves "NOT READY" status in sandbox environments where the agent's working directory differs from the project root

Test plan

  • Validation: all 14 skills pass validate_skills.py
  • Verify env_check.sh reports READY after the fix in sandbox environment

🤖 Generated with claude-flow

Copilot AI review requested due to automatic review settings March 30, 2026 19:53
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes the minimax-docx environment check script to run dotnet restore/dotnet build from inside the .NET project directory, avoiding false “NOT READY” results when the script is executed from a different working directory (common in sandboxed runners).

Changes:

  • cd into DOTNET_DIR before running dotnet restore/dotnet build in env_check.sh.
  • Adjust dotnet restore/dotnet build invocations to rely on the current directory rather than passing DOTNET_DIR as an argument.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 68 to 72
# Try restore + build (cd to DOTNET_DIR to ensure relative paths and native deps resolve correctly)
if cd "$DOTNET_DIR" && dotnet restore --verbosity quiet &>/dev/null; then
printf "[OK] %-14s packages restored\n" "nuget"
if dotnet build "$DOTNET_DIR" --verbosity quiet --no-restore &>/dev/null; then
if dotnet build --verbosity quiet --no-restore &>/dev/null; then
printf "[OK] %-14s build succeeded\n" "project"
Copy link

Copilot AI Mar 30, 2026

Choose a reason for hiding this comment

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

cd "$DOTNET_DIR" changes the script's working directory for the remainder of the checks (and will also leave you in $DOTNET_DIR on the restore-failure path). To avoid hidden side effects, consider running restore/build in a subshell (e.g., (cd ... && dotnet restore && dotnet build ...)) or pushd/popd so later steps always run from the original directory.

Copilot uses AI. Check for mistakes.
In sandbox environments, dotnet CLI must run from the project directory
to correctly resolve native dependencies and relative paths.
This addresses "NOT READY" status in env_check.sh when the agent's
working directory differs from the project root.

Co-Authored-By: claude-flow <ruv@ruvnet>
@JithendraNara JithendraNara force-pushed the fix/minimax-docx-frontmatter branch from aa3403f to 938439f Compare March 30, 2026 20:00
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