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.

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

fix broken links #4924

Merged
merged 1 commit into from
Oct 16, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion content/docs/api-reference/get_url.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ appropriate library, such as [`boto3`] or [`paramiko`].
[`boto3`]:
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/s3.html#S3.Object.download_fileobj
[`paramiko`]:
https://docs.paramiko.org/en/stable/api/sftp.html#paramiko.sftp_client.SFTPClient.get
https://docs.paramiko.org/en/latest/api/sftp.html#paramiko.sftp_client.SFTPClient.get

</admon>

Expand Down
4 changes: 1 addition & 3 deletions content/docs/studio/rest-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,7 @@ the latest version is returned.

When your model is annotated in non-root [`dvc.yaml`] file (typical for monorepo
case), model name will be constructed from two parts separated by colon:
`path/to/dvc/yaml:model_name`. For example, take a look at this
[model from example-get-started-experiments repo](https://studio.iterative.ai/user/aguschin/models/VtQdva13kMSPsN_N8004aQ==/pool-segmentation/v1.0.1).
Its full name that you need to use in API is `results/train:pool-segmentation`.
`path/to/dvc/yaml:model_name`.
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Dropped this example since it's hard to provide a useful link and it's no longer a common scenario since dvclive 3.0 started writing dvc.yaml files to the root of the repo,


| header | desc | example value |
| ------------- | --------------- | ------------- |
Expand Down
2 changes: 1 addition & 1 deletion content/docs/user-guide/upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ Note that when using `--dvc-files` option, DVC will only migrate DVC files in

</admon>

For [DVC remotes](/doc/user-guide/data-magement/remote-storage), there is no
For [DVC remotes](/doc/user-guide/data-management/remote-storage), there is no
equivalent migration command since it is not possible to link between old and
new locations on many remote filesystems. Instead, once you have migrated data
locally and pushed to the remote, you may use `dvc gc -c` commands to remove
Expand Down
Loading