Skip to content

Commit 1fb9eb0

Browse files
committed
err fix + updates
1 parent 50cab97 commit 1fb9eb0

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

docs/artifacts/feeds/project-scoped-feeds.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ monikerRange: '<= azure-devops'
88
"recommendations": "true"
99
---
1010

11-
# Project-scoped vs organization-scoped feeds
11+
# Feed scopes: Project vs organization feeds
1212

1313
[!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)]
1414

@@ -80,8 +80,8 @@ A: If your pipeline is failing to download an artifact from another project, ens
8080

8181
A: Yes, adding users to the Azure DevOps organization is still required for them to access the packages in the feed. You can add them as **Project Collection Valid Users** from **Organization Settings** > **Security** > **Permissions**.
8282

83-
## Related articles
83+
## Related content
8484

85-
- [Configure permissions](./feed-permissions.md)
86-
- [Delete and recover packages](../how-to/delete-and-recover-packages.md)
85+
- [Configure feed permissions](./feed-permissions.md)
8786
- [Use feed views to share packages](./views.md)
87+
- [Delete and recover packages](../how-to/delete-and-recover-packages.md)

docs/artifacts/toc.yml

+2-2
Original file line numberDiff line numberDiff line change
@@ -160,9 +160,9 @@
160160
- name: What are feeds?
161161
displayName: feeds, artifact feeds
162162
href: concepts/feeds.md
163-
- name: Project-scoped vs organization-scoped feeds
164-
displayName: project scoped, feed, artifact feeds
163+
- name: Feed scopes
165164
href: feeds/project-scoped-feeds.md
165+
displayName: project scoped, organization scoped, feed, artifacts
166166
- name: Configure permissions
167167
displayName: feed, artifact feeds, permissions
168168
href: feeds/feed-permissions.md

docs/pipelines/artifacts/pipeline-artifacts.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,7 @@ steps:
161161

162162
---
163163

164-
To download a pipeline artifact from a different project within your organization, make sure that you have the appropriate [permissions](../../artifacts/feeds/project-scoped-feeds.md#how-can-i-download-a-pipeline-artifact-from-another-project-within-the-same-organization) configured for both the downstream project and the pipeline generating the artifact.
164+
To download a pipeline artifact from a different project within your organization, make sure that you have the appropriate [permissions](../../artifacts/feeds/project-scoped-feeds.md#q-how-can-i-download-a-pipeline-artifact-from-another-project-within-the-same-organization) configured for both the downstream project and the pipeline generating the artifact.
165165
By default, files are downloaded to **$(Pipeline.Workspace)**. If an artifact name wasn't specified, a subdirectory will be created for each downloaded artifact. You can use matching patterns to limit which files get downloaded. See [File matching patterns](../tasks/file-matching-patterns.md) for more details.
166166

167167
```yml

0 commit comments

Comments
 (0)