Skip to content

Conversation

@ryzizub
Copy link
Contributor

@ryzizub ryzizub commented Sep 10, 2025

Status

READY

Description

Tool provided for generating the test optimizer bundle have wrong path was generating into wrong directory.

The change in generated bundle is because of changes #1344 where new bundle wasnt generated

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@ryzizub ryzizub self-assigned this Sep 10, 2025
@ryzizub ryzizub requested a review from a team as a code owner September 10, 2025 18:21
@ryzizub ryzizub merged commit 7f8c01b into main Sep 12, 2025
20 checks passed
@ryzizub ryzizub deleted the fix/test-optimizer-script branch September 12, 2025 07:32
@vgvbot vgvbot mentioned this pull request Sep 12, 2025
meylis1998 added a commit to meylis1998/very_good_cli that referenced this pull request Jan 12, 2026
Fixes VeryGoodOpenSource#1360

The previous CI verification using `git diff` could not detect new
untracked files added to the brick. This caused PR VeryGoodOpenSource#1344 to pass CI
with a stale bundle, which was later discovered in PR VeryGoodOpenSource#1358.

Changes:
- Replace simple `git diff` with comprehensive two-part verification
- Check for both modifications AND untracked/deleted bundle files
- Add bundle file path to workflow triggers for direct changes
- Improve error messages with clear remediation steps

The new verification now catches:
- Modified brick files (existing behavior)
- New brick files added (NEW - fixes the bug)
- Deleted brick files (existing behavior)
- Incorrect output paths (NEW)
- Direct bundle modifications (improved)

This ensures the committed bundle always matches what the current
brick source would generate, preventing silent bundle drift.
marcossevilla pushed a commit that referenced this pull request Jan 14, 2026
Fixes #1360

The previous CI verification using `git diff` could not detect new
untracked files added to the brick. This caused PR #1344 to pass CI
with a stale bundle, which was later discovered in PR #1358.

Changes:
- Replace simple `git diff` with comprehensive two-part verification
- Check for both modifications AND untracked/deleted bundle files
- Add bundle file path to workflow triggers for direct changes
- Improve error messages with clear remediation steps

The new verification now catches:
- Modified brick files (existing behavior)
- New brick files added (NEW - fixes the bug)
- Deleted brick files (existing behavior)
- Incorrect output paths (NEW)
- Direct bundle modifications (improved)

This ensures the committed bundle always matches what the current
brick source would generate, preventing silent bundle drift.
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.

3 participants