respect cloneSubmodules as same as forkProcessing #28273
Replies: 2 comments 2 replies
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. To get started, please read our guide on creating a minimal reproduction. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
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 instructionsIf you're running self-hosted, run with 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.
-
Tell us more.
yes, we had an bug for that ;)
#8936 from @andreibsk
but stalled and being closed by bot
Suggestion: allow
cloneSubmodules
to be respected as likeforkProcessing
inonboardingConfigFileName
Issue to solve: clone of repository and submodule processing is made before project config is read! That leads to the case, that a private submodule (from sight of renovate on a self-hosted instance) can't be cloned and repository processing fails.
The project config
cloneSubmodules: false
is being ignoredProposal to fix: as like forkProcessing, the config might be altered in https://github.com/renovatebot/renovate/blob/main/lib/workers/repository/init/apis.ts
to be checked: https://github.com/renovatebot/renovate/blob/main/lib/workers/repository/init/index.ts#L69 is being processed after config merge so there shouldn't be an issue at all, but rundown says.
perhaps the forkProcessing Feature itself corrupted this by
initRepo
! https://github.com/renovatebot/renovate/blob/main/lib/workers/repository/init/apis.ts#L97ref behavior of forkProcessing as documented:
Beta Was this translation helpful? Give feedback.
All reactions