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

Assess the repository links and use relative links where feasible #3535

Open
2 tasks done
corbob opened this issue Oct 25, 2024 · 0 comments
Open
2 tasks done

Assess the repository links and use relative links where feasible #3535

corbob opened this issue Oct 25, 2024 · 0 comments

Comments

@corbob
Copy link
Member

corbob commented Oct 25, 2024

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

No response

Describe The Solution. Why is it needed?

A number of the links in various markdown files are absolute links to files on either the master of develop branch of the repository. Where it's appropriate we should consider using relative links.

Additional Context

As noted, some go to master and others go to develop. I think this is intentional, and possibly desired for some of the links. It seemed that the ones that went to master were around licensing and the libraries used by Chocolatey CLI, which I think makes sense as people interested in those are likely looking for information on the released product.

Related Issues

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant