feat: add --result-json-file option for programmatic result processing #44
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
--result-json-file
option to output sync results as JSONMotivation
Closes #2
This feature enables CI/CD pipelines to programmatically determine which files have changed during sync operations. The JSON output can be used to:
Changes
--result-json-file <path>
changes
: Array of file change detailssummary
: Statistics (created, updated, deleted, failed)create
andupdate
based on the sync reasonJSON Output Format
Create/Update Operations
Delete Operations
Complete Example
Breaking Changes
from
/to
tosource
/target
patterntarget
field (nosource
)skip
field from summaryThis structure provides clearer semantics and enables future extensibility for S3-to-local and S3-to-S3 sync operations.
Test Plan
🤖 Generated with Claude Code