Is there a configuration option for fullClone?

[chopeen]

What would you like help with?

Other

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

GitLab + Renovate image 38.46-full

Please tell us more about your question or problem

What the configuration option that corresponds with config.fullClone below?

renovate/lib/util/git/index.ts

Lines 417 to 422 in 65b4212

	if (config.fullClone) {
	logger.debug('Performing full clone');
	} else {
	logger.debug('Performing blobless clone');
	opts.push('--filter=blob:none');
	}

I checked configuration-options and self-hosted-configuration, I did not find any.

---

I have a certain repository that gets cloned and then the scanning process shows a series of has no content debug messages for all the files:

2024-08-20T10:02:44.988330Z 01O DEBUG: vue_frontend/src/store/mutations.js has no content
2024-08-20T10:02:44.988453Z 01O DEBUG: vue_frontend/src/store/otss/actions.js has no content
2024-08-20T10:02:44.988587Z 01O DEBUG: vue_frontend/src/store/otss/getters.js has no content
2024-08-20T10:02:44.988710Z 01O DEBUG: vue_frontend/src/store/otss/index.js has no content

I would like to test if changing the cloning mode could fix that.

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[rarkins]

There is no such exposed configuration option today

[darlanalves]

As an alternative, you can do the git clone outside of Renovate, then point the tool to it.

If you look at the same file listed above, before the code enters the clone path, it will first check for the presence of .git/HEAD inside the current working repository.

If Renovate is working on an existing full clone, then only a git fetch/pull, followed by a few resets, will happen instead.

[darlanalves]

If you run with Docker it's easy. Add a volume with your cloned repo:

docker run ... -v $PWD:/tmp/renovate/repos/gitlab/org/repo

[viceice]

you should analyze why the content is missing instead of doing hacky workarounds.

[chopeen]

After some further digging, I can tell this message had nothing to do with cloning the code.

It is logged at manager-files.ts#L71 and there is a message for every single file in the repository, because I have the custom aws-machine-image manager configured with fileMatch: [".*"]. This custom manager loads every file and failing to find any AMIs logs the message has no content.