Skip to content

fix(git): Remove obsolete cleanup for renovate temp refs#34356

Merged
rarkins merged 1 commit intorenovatebot:mainfrom
zharinov:feat/remove-obsolete-ref-cleanup
Feb 20, 2025
Merged

fix(git): Remove obsolete cleanup for renovate temp refs#34356
rarkins merged 1 commit intorenovatebot:mainfrom
zharinov:feat/remove-obsolete-ref-cleanup

Conversation

@zharinov
Copy link
Copy Markdown
Collaborator

@zharinov zharinov commented Feb 20, 2025

Changes

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 select 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

@rarkins
Copy link
Copy Markdown
Contributor

rarkins commented Feb 20, 2025

Is this really a feat and not fix or refactor?

@zharinov
Copy link
Copy Markdown
Collaborator Author

At this point I'm confused, before recently we were renaming all the branches that do any refactor that does change behavior

@rarkins
Copy link
Copy Markdown
Contributor

rarkins commented Feb 20, 2025

Is it a fix, if it's cleanup behavior which was missed in the earlier PR?

@zharinov zharinov changed the title feat(git): Remove obsolete cleanup for renovate temp refs fix(git): Remove obsolete cleanup for renovate temp refs Feb 20, 2025
@zharinov
Copy link
Copy Markdown
Collaborator Author

Yes, it only cleans up refs/renovate/branches/* now

@rarkins rarkins added this pull request to the merge queue Feb 20, 2025
Merged via the queue into renovatebot:main with commit 02be094 Feb 20, 2025
@rarkins rarkins deleted the feat/remove-obsolete-ref-cleanup branch February 20, 2025 18:54
@renovate-release
Copy link
Copy Markdown

🎉 This PR is included in version 39.177.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Mar 25, 2025
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.

4 participants