Skip to content

docs(state): qualify legacy lusoris/vmaf issue + PR refs after VMAFx migration #408

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lusoris merged 1 commit into from
May 31, 2026
Merged

docs(state): qualify legacy lusoris/vmaf issue + PR refs after VMAFx migration #408

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions changelog.d/changed/state-md-github-issues-crossref.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
- **docs(state):** Cross-reference `docs/state.md` against `VMAFx/vmafx`
GitHub Issues. The repo carries **0 issues** (only PRs); the historical
bug-tracker numbers cited in `state.md` (`#239`, `#857`, plus the
resolving PR refs `#241`, `#310`, `#870`) live on the archived
`lusoris/vmaf` repo and collide with unrelated PR numbers on
`VMAFx/vmafx`. Qualified every bare cite as `lusoris/vmaf#NNN` so future
maintainers don't follow ambiguous numbers to a different PR on the
active repo. No issues were closed and no rows added — repo state was
already aligned; this PR is documentation hygiene only.
Loading
Loading