Add docs for baseline diff - #584
Conversation
| ## Examples | ||
|
|
||
| Compare two specific release tags for a manifest that uses the builtin registry: | ||
|
|
||
| ```console | ||
| vcpkg x-baseline-diff 2024.11.16 2024.12.16 | ||
| ``` | ||
|
|
||
| Compare two commit SHAs explicitly: | ||
|
|
||
| ```console | ||
| vcpkg x-baseline-diff 5507daa796359fe8d45418e694328e878ac2b82f 9291e3e1d8e4a3d7a9f8b2c1f0e5d6c7b8a9e0f1 | ||
| ``` | ||
|
|
||
| Use the one-argument form after running `x-update-baseline` — the current | ||
| `builtin-baseline` in `vcpkg.json` is used as the old baseline: | ||
|
|
||
| ```console | ||
| vcpkg x-update-baseline | ||
| vcpkg x-baseline-diff 2026.03.18 | ||
| ``` | ||
|
|
||
| Compare two named baselines in a filesystem registry: | ||
|
|
||
| ```console | ||
| vcpkg x-baseline-diff v1 v2 | ||
| ``` | ||
|
|
There was a problem hiding this comment.
I think we do not need this. Other opinions?
|
Learn Build status updates of commit e410308: ✅ Validation status: passed
For more details, please refer to the build report. |
PRMerger Results
|
PoliCheck Scan ReportThe following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans. ✅ No issues foundMore information about PoliCheckInformation: PoliCheck | Severity Guidance | Term |
Mostly written by claude code.