Don't update statuses to offline again and again #27375
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
nickvergessen
requested review from
blizzz,
juliusknorr,
kesselb,
artonge and
skjnldsv
|
/backport to stable21 |
|
/backport to stable20 |
|
/backport to stable19 |
nickvergessen
added
2. developing
nickvergessen
removed request for
blizzz,
juliusknorr,
kesselb,
artonge and
skjnldsv
Signed-off-by: Joas Schilling <coding@schilljs.com>
nickvergessen
force-pushed
the
bugfix/noid/dont-update-offline-status
branch
from
f759181
to
55c4458
Compare
nickvergessen
requested review from
juliusknorr,
kesselb,
skjnldsv,
artonge and
blizzz
nickvergessen
added
3. to review
blizzz
approved these changes
Jun 7, 2021
skjnldsv
approved these changes
Jun 7, 2021
This was referenced Jun 7, 2021
|
The backport to stable19 failed. Please do this backport manually. |
|
Right, status is 20+ |
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.
Otherwise the user is updated and pushed to the dashboard over and over again
(was visible with Sascha on our instance, hotfix applied)