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

OSAL Configuration Guide Link is broken in README #961

Closed
rosspeters6 opened this issue Apr 14, 2021 · 0 comments · Fixed by #962 or #1058
Closed

OSAL Configuration Guide Link is broken in README #961

rosspeters6 opened this issue Apr 14, 2021 · 0 comments · Fixed by #962 or #1058
Assignees
Labels
Milestone

Comments

@rosspeters6
Copy link
Contributor

Describe the bug
The link to the OSAL Configuration Guide is broken in blob/main/README.md.

To Reproduce
Go to https://github.com/nasa/osal/blob/main/README.md and then click on the "Configuration Guide" link near the bottom of the file. It navigates to the old PDF file link.

Expected behavior
I expected the link to take me to the Markdown file in the repo.

Code snips
See the [Configuration Guide](https://github.com/nasa/osal/blob/master/doc/OSAL-Configuration-guide.pdf) for more information. (should reference doc/OSAL-Configuration-Guide.md).

System observed on:
Documentation only.

Additional context
N/A

Reporter Info
Ross Peters

@skliper skliper added the docs label Apr 14, 2021
@astrogeco astrogeco self-assigned this May 5, 2021
astrogeco added a commit that referenced this issue Jun 2, 2021
…uide-link

Fix #961, update OSAL Config Guide link
pepepr08 pushed a commit to pepepr08/osal that referenced this issue Jun 9, 2021
@skliper skliper added this to the 6.0.0 milestone Sep 24, 2021
jphickey pushed a commit to jphickey/osal that referenced this issue Aug 10, 2022
jphickey pushed a commit to jphickey/osal that referenced this issue Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants