From 686bd080f0cf10c9d1a10e885bc3fb3be1100b1c Mon Sep 17 00:00:00 2001 From: Madison Swain-Bowden Date: Sun, 10 Dec 2023 17:47:06 -0800 Subject: [PATCH] Update links to archived repositories in documentation (#3502) --- documentation/general/contributing.md | 6 +++--- documentation/general/publish.md | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/documentation/general/contributing.md b/documentation/general/contributing.md index 57ead193446..542b729be15 100644 --- a/documentation/general/contributing.md +++ b/documentation/general/contributing.md @@ -95,7 +95,7 @@ that do not involve working with code at all. Some of them are listed below. If you'd like to contribute to the design, feel free to propose a solution to an existing problem labeled with -[Needs Design](https://github.com/WordPress/openverse-frontend/issues?q=is%3Aopen+is%3Aissue+label%3A%22needs+design%22), +[Needs Design](https://github.com/WordPress/openverse/issues?q=is%3Aopen+is%3Aissue+label%3A%22design%3A+needed%22+), or share an idea if you think it meets Openverse's goals. The [WordPress Design team](https://make.wordpress.org/design/) uses @@ -123,14 +123,14 @@ contributing this information back to the documentation is very much appreciated. Once you are done and ready to share your idea, -[create an issue with the `design` label and fill in the template](https://github.com/WordPress/openverse-frontend/issues/new?assignees=&labels=🖼️+aspect%3A+design%2C✨+goal%3A+improvement%2C+🚦+status%3A+awaiting+triage&template=feature_request.md&title=). +[create an issue with the `design` label and fill in the template](https://github.com/WordPress/openverse/issues/new?assignees=&labels=🖼️+aspect%3A+design%2C✨+goal%3A+improvement%2C+🚦+status%3A+awaiting+triage&template=feature_request.md&title=). Please be as specific and concise as possible and feel free to add mockups, prototypes, videos, sketches, and anything that makes your idea easier to understand. After creating the issue, it will be labeled with `aspect: design`. Please reference -[existing design issues](https://github.com/WordPress/openverse-frontend/issues?q=is%3Aopen+is%3Aissue+label%3A%22%F0%9F%96%BC%EF%B8%8F+aspect%3A+design%22) +[existing design issues](https://github.com/WordPress/openverse/issues?q=is%3Aopen+is%3Aissue+label%3A%22%F0%9F%96%BC%EF%B8%8F+aspect%3A+design%22) as a guide for how to describe your solution and to understand how the discussion evolves before implementation begins. diff --git a/documentation/general/publish.md b/documentation/general/publish.md index f218fd2735c..3892450f562 100644 --- a/documentation/general/publish.md +++ b/documentation/general/publish.md @@ -51,8 +51,8 @@ the last 90 days _Note: [GitHub's documentation provides screenshots for the various steps](https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch)_ -1. Navigate to the `openverse-api` "Actions" tab in GitHub: - [github.com/WordPress/openverse-api/actions](https://github.com/WordPress/openverse-api/actions). +1. Navigate to the `openverse` "Actions" tab in GitHub: + [github.com/WordPress/openverse/actions](https://github.com/WordPress/openverse/actions). 2. Select the "Publish Docker images on-demand" workflow. 3. Click the "Run workflow" button. 1. (Optional) change the branch _that the workflow is running from_ (this