Replace/remove references to defunct freenode instance (#16873) #16897
+19
−21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
💔 Build Failed
Failed CI StepsHistory |
The preferred channel for communication about LS is the elastic discussion forum, this commit updates the source code and readme files to reflect that.
donoghuc
force-pushed
the
backport-freenode-replacement-8.x
branch
from
1983e8a to
6c3bb8c
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport PR #16873 to 8.x branch, original message:
Release notes
[rn:skip]
What does this PR do?
Remove references to defunct freenode IRC and replace with preferred discussion forum.
Why is it important/What is the impact to the user?
Point folks at the preferred public discussion forum.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding change to the default configuration files (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksRelated issues
Closes #16851