Skip to content

feat(poly sync): non-interactive mode when running in quite mode#390

Merged
DavidVujic merged 3 commits intomainfrom
389-poly-sync-non-interactive
Nov 1, 2025
Merged

feat(poly sync): non-interactive mode when running in quite mode#390
DavidVujic merged 3 commits intomainfrom
389-poly-sync-non-interactive

Conversation

@DavidVujic
Copy link
Owner

@DavidVujic DavidVujic commented Nov 1, 2025

Description

The poly sync command shouldn't run in interactive mode (i.e. ask about adding bricks to empty projects) when running in the --quiet mode.

The quiet mode will perform the sync action without any output. For scenarios where you want a notification about any unstaged changes, you can use the git diff command in a script (and use the script in your pre-commit hook or similar):

if ! git diff --quiet; then
  echo "You have unstaged changes."
  exit 1
fi

Motivation and Context

Fixes #389

When running the poly sync command in an automated flow

How Has This Been Tested?

✅ CI
✅ Unit test
✅ local run of command with empty project and unused brick, with and without the --quiet option

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

@sonarqubecloud
Copy link

sonarqubecloud bot commented Nov 1, 2025

@DavidVujic DavidVujic merged commit 7a10007 into main Nov 1, 2025
4 checks passed
@DavidVujic DavidVujic deleted the 389-poly-sync-non-interactive branch November 1, 2025 08:22
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.

poly sync with a non-interactive option

1 participant