Remove Go-NEB #4716
Draft
Remove Go-NEB #4716
Conversation
This file contains hidden or 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
Contributor
|
A bit off-topic, but does it still make sense to keep the sliding sync proxy around? |
Collaborator
Author
|
If there is not something which uses it then it should be fine to remove it, but I am not sure if there is one or not. |
Owner
|
Yes, sliding-sync should be fine to remove. It's long been replaced with native sliding sync. |
Collaborator
Author
|
I'm taking care of it soon! |
Reuse https://github.com/spantaleev/matrix-docker-ansible-deploy/blob/096b85bd966931c6ddca8196829c4b99f2fb664f/docs/configuring-playbook-email2matrix.md Signed-off-by: Suguru Hirahara <did:key:z6MkvVZk1A3KBApWJXv2Ju4H14ErDfRGxh8zxdXSZ4vACDg5>
luixxiul
force-pushed
the
remove-bot-go-neb
branch
from
dec901e to
8878eed
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
It does not feel nice to remove components in a row, but it does not make sense to keep what's been deprecated by the upstream in the playbook, and reducing tech debt will improve quality of the playbook down the road.