Skip to content

fix: use repo-relative artifact paths#87

Merged
taylor-01 merged 3 commits into
mainfrom
codex/bit-294-generic-paths
May 14, 2026
Merged

fix: use repo-relative artifact paths#87
taylor-01 merged 3 commits into
mainfrom
codex/bit-294-generic-paths

Conversation

@taylor-01
Copy link
Copy Markdown
Contributor

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.

@taylor-01 taylor-01 requested a review from a team as a code owner May 14, 2026 20:41
@taylor-01 taylor-01 force-pushed the codex/bit-294-generic-paths branch from 078f337 to 32501ec Compare May 14, 2026 20:42
@taylor-01 taylor-01 force-pushed the codex/bit-294-generic-paths branch from 71e9a2b to 5863ebf Compare May 14, 2026 20:50
Copy link
Copy Markdown
Member

@cjarguello cjarguello left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@taylor-01 taylor-01 merged commit cc4b89f into main May 14, 2026
1 check passed
@taylor-01 taylor-01 deleted the codex/bit-294-generic-paths branch May 14, 2026 21:05
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.

2 participants