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

docs(site): edit page button on zarf docs site takes you to wrong path on github #2642

Closed
joelmccoy opened this issue Jun 20, 2024 · 0 comments · Fixed by #2650
Closed

docs(site): edit page button on zarf docs site takes you to wrong path on github #2642

joelmccoy opened this issue Jun 20, 2024 · 0 comments · Fixed by #2650

Comments

@joelmccoy
Copy link
Contributor

Environment

Device and OS: N/A
App version: N/A
Kubernetes distro being used: N/A
Other: N/A

Steps to reproduce

  1. Visit a zarf page such as this tutorial and click on "Edit Page"
    image
  2. This takes you to an invalid github link

Expected result

  1. Takes you to a valid github link for the example provided

Actual Result

  1. Takes you to an invalid link (possibly an old path)

Visual Proof (screenshots, videos, text, etc)

image

Severity/Priority

Low

Additional Context

It just looks like the paths for the docs in the github repo have changed and will need to be updated accordingly on the docs site.

@AustinAbro321 AustinAbro321 mentioned this issue Jun 20, 2024
2 tasks
AustinAbro321 added a commit that referenced this issue Jul 23, 2024
## Description

Fixes all the links checked by linkinator. Not checking github since it
gives bad error codes even if the site link works

## Related Issue

Fixes #2642 and #2643

## Checklist before merging

- [ ] Test, docs, adr added or updated as needed
- [ ] [Contributor Guide
Steps](https://github.com/defenseunicorns/zarf/blob/main/.github/CONTRIBUTING.md#developer-workflow)
followed

Signed-off-by: Austin Abro <AustinAbro321@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant