Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: yuya-takeyama/strict-s3-sync
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v0.0.12
Choose a base ref
...
head repository: yuya-takeyama/strict-s3-sync
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v0.1.0
Choose a head ref
  • 2 commits
  • 3 files changed
  • 2 contributors

Commits on Aug 3, 2025

  1. feat: add --result-json-file option for programmatic result processing ( 

    #44)

* feat: add --result-json-file option for programmatic result processing

- Added new CLI flag to output sync results to a JSON file
- Structured output includes file changes and summary statistics
- Distinguish between create and update actions based on file reason
- Support for both dry-run and actual execution modes
- Useful for CI/CD pipelines to determine changed files

Closes #2

* fix: remove unused skip action from JSON output

- Removed skip field from Summary struct
- Removed ActionSkip handling in both dry-run and execution modes
- Updated README to reflect that only create, update, and delete actions are supported
- Skip action was never actually used since planner only returns items that need action

* refactor\!: change JSON output to use from/to paths for future extensibility

BREAKING CHANGE: JSON output structure has changed
- Replaced path, local_path, s3_key, bucket fields with from and to
- from: absolute source path (e.g., /path/to/file or s3://bucket/key)
- to: absolute destination path (empty string for deletions)
- This enables consistent output for future S3-to-local and S3-to-S3 operations

* refactor\!: change JSON output to use source/target pattern

BREAKING CHANGE: JSON output structure has changed again
- Replaced from/to with source/target pattern
- create/update: source (local path) and target (S3 path)
- delete: only target (S3 path to delete), no source field
- This provides clearer semantics for each action type
    @yuya-takeyama
    yuya-takeyama authored Aug 3, 2025
    Configuration menu
    Copy the full SHA
    2d12640 View commit details
    Browse the repository at this point in the history

  2. Release for v0.1.0 (#45) 

    * [tagpr] prepare for the next release

* [tagpr] update CHANGELOG.md

---------

Co-authored-by: yuya-takeyama-tagpr[bot] <224357098+yuya-takeyama-tagpr[bot]@users.noreply.github.com>
    @yuya-takeyama-tagpr
    yuya-takeyama-tagpr[bot] authored Aug 3, 2025
    Configuration menu
    Copy the full SHA
    ad4c3d2 View commit details
    Browse the repository at this point in the history
Loading