New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(config): validate reconfigure branch #24699
feat(config): validate reconfigure branch #24699
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Since we do not control the creation of this branch, shuold we ignore while pruning stale branches? |
yes, we should ignore it when pruning |
Test runs:
On re-runs there was no cloning, tested it locally. |
Also needs docs added |
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
…autamSingh/renovate into rename-second-parsePreset
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Co-authored-by: Rhys Arkins <rhys@arkins.net>
Re-run the tests for confirmation, All working ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
🎉 This PR is included in version 37.44.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Co-authored-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Co-authored-by: Rhys Arkins <rhys@arkins.net> Co-authored-by: Sebastian Poxhofer <secustor@users.noreply.github.com> Co-authored-by: Michael Kriese <michael.kriese@visualon.de>
Changes
Context
Closes: #13948
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: