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

Link to SSH keys role in README results in 404 #306

Closed
Lyannic opened this issue Aug 13, 2024 · 0 comments · Fixed by #308
Closed

Link to SSH keys role in README results in 404 #306

Lyannic opened this issue Aug 13, 2024 · 0 comments · Fixed by #308
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@Lyannic
Copy link

Lyannic commented Aug 13, 2024

Description

When clicking the link to the SSH keys role in the README, a 404 page is being displayed.

To reproduce

  1. Open the project's README at https://github.com/hifis-net/ansible-collection-toolkit
  2. Click on the link SSH key in the bullet point distribute authorized SSH keys to users
  3. See that GitHub shows a 404 page

Current behavior

A 404 page is being displayed

Expected behavior

The SSH key role directory is displayed

OS / Environment

Not OS and environment dependent

Ansible version

Has nothing to do with Ansible

Collection version

v4.7.0

Additional context

The current link is https://github.com/hifis-net/ansible-collection-toolkit/blob/main/role/ssh_keys. I think that it is supposed to be https://github.com/hifis-net/ansible-collection-toolkit/tree/main/roles/ssh_keys.

@Lyannic Lyannic added the bug Something isn't working label Aug 13, 2024
@tobiashuste tobiashuste self-assigned this Aug 16, 2024
@tobiashuste tobiashuste added documentation Improvements or additions to documentation and removed bug Something isn't working labels Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants