fix: Add workingdir warning and improve documentation#23
Open
fix: Add workingdir warning and improve documentation#23
Conversation
- Add warning when command runs from repo root but may need subdirectory - Rewrite README with usage examples, input tables, and common issues - Add CI tests for subdirectory builds (with/without workingdir) - Add test fixtures to simulate monorepo structure - Add unit tests for command flow and input handling The warning helps users in monorepos discover they need to set the `workingdir` input when their Makefile/Dockerfile is in a subdirectory. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
colek42
force-pushed
the
fix/workingdir-warning-and-docs
branch
from
a5ffe06 to
eff0083
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Problem
Users in monorepos were experiencing silent build failures because the wrapper always runs from GITHUB_WORKSPACE (repo root), not from the subdirectory where their Makefile/Dockerfile lives.
Solution
Test plan