Skip to content

Remove vendor from git and generate with CI

Ghost User requested to merge ci_save_vendor into main

This is just an idea I'd like to get feedback on. We may have other reasons for committing the vendor tree that weren't apparent to me. /cc @kali for feedback on whether this is a good idea or not?

Previously we saved the vendor tree in version control, making any commit that changed a dependency rather large. Go Modules gives us most of the advantages of vendoring except that if a dependency which is not stored on the proxy is deleted we would lose access to it. Instead of keeping the vendor tree in version control, generate it and back it up each time CI is run so that if we do lose access we can pull the bad project out of the archive and we'll still be able to build.

Signed-off-by: Sam Whited sam@samwhited.com

Merge request reports