From b9d63d4e2a81f849ba18fac72253ed9c4fe513a4 Mon Sep 17 00:00:00 2001 From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Date: Wed, 23 Mar 2022 11:29:30 +0100 Subject: [PATCH] docs: rewrite gitlab security paragraph (#14706) Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Rhys Arkins <rhys@arkins.net> --- docs/usage/gitlab-bot-security.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/usage/gitlab-bot-security.md b/docs/usage/gitlab-bot-security.md index f7e07cfcd7..063e6b2eda 100644 --- a/docs/usage/gitlab-bot-security.md +++ b/docs/usage/gitlab-bot-security.md @@ -80,8 +80,8 @@ Bot services are better if they are provisioned with a "bot identity" so that us Until the hosted app can be reactivated, we recommend users migrate to use self-hosted pipelines to run Renovate. Please see the [renovate-bot/renovate-runner README on GitLab](https://gitlab.com/renovate-bot/renovate-runner/-/blob/HEAD/README.md) for instructions on how to set this up as easily as possible. -The Renovate team is working to find a feasible design for the app so that we can reactive it securely in future. -We welcome any ideas you may have. +We're trying to find a workable design for the GitLab app, so we can enable it safely again. +If you have any ideas, open a [discussion](https://github.com/renovatebot/renovate/discussions) and let us know! ## Acknowledgments -- GitLab