THIS IS A FEATURE REQUEST:

Actually running ct lint on limited connectivity work envs (air gap / train / plain / slow connectivity) give a limited experience, because ct lint is doing a helm depency build even if the awaited tgz are already present.
This also can in some cases lead to unwanted changes to be added to git HEAD (tgz modifications with same versions but different rights or just corrupted during download)

I would suggest adding a flag (and such option in ct.yaml) to allow skipping it.

I guess there are 2 possible ways to implement :

• skip the helm dependency build if tgz are present, but we can't guarantee they are fresh enough
• skip the whole step, relying on the user to do dependency build before running ct

what do you think ?