Repository navigation
fix(backupcodes): Remove old notifications before creating a new remi… - #41447
Merged
Merged
Conversation
…nder Signed-off-by: Joas Schilling <coding@schilljs.com>
nickvergessen
requested review from
ChristophWurst,
miaulalala and
st3iny
as code owners
November 14, 2023 07:53
Member
Author
|
/backport to stable27 |
Member
Author
|
/backport to stable26 |
ChristophWurst
approved these changes
Nov 14, 2023
bigcat88
approved these changes
Nov 14, 2023
Merged
This was referenced Nov 14, 2023
4 tasks done
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
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.
…nder
Summary
Currently a user will receive a new notification every 2 weeks. Previous notifications however did not get removed before, resulting in some users having multiple (record seen in the wild is 68 notifications => 952 days so over 2 years ignoring this).
Checklist