Add mailing list to README #1023
Merged
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
Co-authored-by: tison <wander4096@gmail.com>
|
@PragmaTwice we can have a path filter for skipping CI on docs change. But since we required the status, it can be a bit tricky and we should make use of https://github.com/dorny/paths-filter to skip steps. It's not a requirement of this patch, of course. |
tisonkun
approved these changes
Oct 21, 2022
Sure, we need to skip CI if no actual code changes. |
|
Let me create an issue for it. |
manchurio
pushed a commit
to manchurio/kvrocks
that referenced
this pull request
Oct 21, 2022
* Add mailing list to README * Update .asf.yaml * Update README.md Co-authored-by: tison <wander4096@gmail.com> Co-authored-by: tison <wander4096@gmail.com>
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.
Since
dev@is already overwhelmed with discussion messages, and I always get duplicated discussion notification mails from both github anddev@), I thought I could move the discussion notifications toissues@as well.I also removed the google group link because it has not been used for a long time and many developers canot get notifications. Is this appropriate? @git-hulk