Disabled because a matching PR was automerged previously. #31169
Replies: 1 comment 5 replies
-
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.
-
Hi all,
We self host renovate by running the NPM package in an azure devops pipeline on a 4hr schedule. This works brilliantly for all the rest of our repositories except for the renovate repository itself which now gives the above message on minor increments only. We have modified the config to disable automerge and autoComplete then re-enabled, crawled through PRs to see if we can find when this happened and the only thing that stands out is it seemed to happen after we migrated to v38.x from v37.x
How else might we resolve this?
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions