Skip to content
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

chore: improve logging for stale branch rebase #13009

Merged

Conversation

osigida
Copy link
Contributor

@osigida osigida commented Dec 8, 2021

Changes:

Debug log lines added to clarify stale branch reuse decision flow

Context:

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

@osigida osigida force-pushed the reuse-bracnh-if-it-was-not-modified branch from 5d6d32a to a25bbcc Compare December 8, 2021 13:30
lib/workers/branch/reuse.ts Outdated Show resolved Hide resolved
Co-authored-by: Rhys Arkins <rhys@arkins.net>
@rarkins rarkins changed the title feat: improve logging for branch reuse decision flow #13004 logs: improve logging for stale branch rebase Dec 8, 2021
@rarkins rarkins changed the title logs: improve logging for stale branch rebase chore: improve logging for stale branch rebase Dec 8, 2021
@rarkins rarkins enabled auto-merge (squash) December 8, 2021 14:25
@rarkins rarkins merged commit 12f467a into renovatebot:main Dec 8, 2021
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 29.36.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants