feat(rooms): add option to automatically lock public and group rooms #13779
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
miaulalala
added
2. developing
feature: api 🛠️
|
/backport to stable30 |
Not for now |
miaulalala
force-pushed
the
feat/lock-rooms-after-inactivity
branch
from
5004c66 to
991be3a
Compare
miaulalala
force-pushed
the
feat/lock-rooms-after-inactivity
branch
from
991be3a to
cd8986a
Compare
…if they are inactive Signed-off-by: Anna Larch <anna@nextcloud.com>
miaulalala
force-pushed
the
feat/lock-rooms-after-inactivity
branch
from
cd8986a to
f11783e
Compare
2 tasks
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.
…if they are inactive
Question - do we need to limit the room numbers to a certain amount per run of the BG job?
☑️ Resolves
🛠️ API Checklist
🚧 Tasks
🏁 Checklist
docs/has been updated or is not required