Renovate is force-pushing over a change made by another user #33170
Replies: 1 comment
-
Hi there, This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions. No logs at allIf you haven't posted any log yet, we need you to find and copy/paste the log into the issue template. Finding logs on hosted appSelect me to read instructionsIf you use the Mend Renovate app (GitHub):
Finding logs when self-hostingSelect me to read instructionsRead the Renovate docs, troubleshooting, self-hosted to learn how to find the logs. Insufficient logsSelect me to read instructionsIf you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section. Formatting your logsSelect me to read instructionsPlease put your logs in a
If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Github Actions using the official GHA, latest version
Please tell us more about your question or problem
Hey team,
Renovate has been force-pushing on a branch, erasing some collaborator's test fixes before we could get them merged.
A new version of the package was available, can it be related? We expected Renovate not to touch anything on top of another user's commit.
Thanks
Logs (if relevant)
No response
Beta Was this translation helpful? Give feedback.
All reactions