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

Broken link in documentation: Test the changes in developer.md #463

Open
Nageshbansal opened this issue May 18, 2023 · 3 comments · May be fixed by #501
Open

Broken link in documentation: Test the changes in developer.md #463

Nageshbansal opened this issue May 18, 2023 · 3 comments · May be fixed by #501
Assignees

Comments

@Nageshbansal
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST?

Choose one: BUG REPORT or FEATURE REQUEST
BUG REPORT

What happened:
I would like to report a broken link in the documentation for the Test the changes in developer.md section. The broken link can be found on the pointer: "Run the chaos by following the Litmus Docs." When I click the link, it leads to a 404 error page.

What you expected to happen:
The link should direct me to the correct resource or page related to the topic mentioned in the documentation.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:
Update the link in the documentation to point to the correct resource or page, or remove the broken link altogether if the resource is no longer available

@Nageshbansal
Copy link
Contributor Author

Nageshbansal commented May 18, 2023

I believe it is necessary to replace the broken link with the following URL: https://docs.litmuschaos.io/docs/getting-started/run-your-first-workflow/. Please confirm if this is accurate, and I will proceed to create a pull request (PR) for the same.

@Nageshbansal
Copy link
Contributor Author

cc @ispeakc0de @ksatchit

@neelanjan00
Copy link
Member

Please go ahead and raise the PR @Nageshbansal, thanks for reporting this!

@andoriyaprashant andoriyaprashant linked a pull request Jul 23, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants