-
-
Notifications
You must be signed in to change notification settings - Fork 251
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] Dead Link in Readme #518
Comments
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
It's going stale because it hasn't been responded to by the project, it is not (AFAIK) waiting on feedback from me. |
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
It's going stale because it hasn't been responded to by the project, it is not (AFAIK) waiting on feedback from me. |
Any interest into my suggested template updates? |
This was included in #534 |
believe OP is asking about the issue template which assumes every issue is related to a container, rather than potentially documentation, like this. |
You are correct, sir! |
Ah. It's something we could look at, we don't get many docs related issues but it's not a huge amount of work to distribute a new template. We'll discuss it and see if it makes sense to do. |
Consider this: The absence of a documentation template may discourage potential issues from being logged. |
Is there an existing issue for this?
Current Behavior
The readme file has the following point in the last line of the "Using fail2ban" section:
Unfortunately, the link is dead and there seems to be no current list of all commands on their GitHub wiki. The closest thing I could find is where the commands are built into the code, or else I would have PR'd a fix.
It's a shame that the upstream project's documentation is not as complete as it was in the past. The best thing this project can do is probably to just remove the line, unless there's other documentation I'm missing.
Expected Behavior
No response
Steps To Reproduce
Oh good, the template has all these required fields.
Environment
No response
CPU architecture
x86-64
Docker creation
I guess I'll use them to suggest that you make a new template.
Container logs
The text was updated successfully, but these errors were encountered: