fix: use repo-relative artifact paths#87
Merged
Conversation
078f337 to
32501ec
Compare
71e9a2b to
5863ebf
Compare
cjarguello
approved these changes
May 14, 2026
Member
cjarguello
left a comment
There was a problem hiding this comment.
LGTM — Path migration is consistent (storage/sync/ops/intake/track_reports now emit repo-relative paths and scripts now resolve from repo root), targeted tests passed (tests/test_storage.py, tests/test_sync_filtering.py, tests/test_track_reports.py), and I found no blocking issues in this PR.
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
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.
Aligns status/permalink and report paths to repo-relative values instead of absolute machine-specific paths for portability across environments. Includes storage, sync, ops, track, and permalink scripts.