Skip to content
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

Jump to bottom

[vcpkg docs] Update the versioning.getting-started.md #16324

Merged
merged 1 commit into from
Feb 21, 2021
Merged

[vcpkg docs] Update the versioning.getting-started.md #16324

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/users/versioning.getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,7 @@ Create a folder with the following files:
**main.cpp**
```c++
#include <fmt/core.h>
#include <zlib.h>

int main()
{
Expand Down Expand Up @@ -160,7 +161,7 @@ If you want to upgrade your dependencies, you can bump the minimum version const
"builtin-baseline": "b60f003ccf5fe8613d029f49f835c8929a66eb61"
```

This field declares the versioning baseline for all ports. But what is a baseline? What does it do? Why is the value a SHA?
This field declares the versioning baseline for all ports. Setting a baseline is required to enable versioning, otherwise you will get the current versions on the ports directory. You can run 'git rev-parse HEAD' to get the current commit of vcpkg and set it as the builtin-baseline. But what is a baseline? What does it do? Why is the value a SHA?

From the [versioning documentation](versioning.md):

Expand Down