Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

Support for bazel / dep check extra configuration #2033

Closed
rubensf opened this issue Oct 4, 2018 · 1 comment
Closed

Support for bazel / dep check extra configuration #2033

rubensf opened this issue Oct 4, 2018 · 1 comment

Comments

@rubensf
Copy link

rubensf commented Oct 4, 2018

Hey! I'm using dep, bazel and gazelle on a project - my problem is, gazelle puts a bunch of BUILD.bazel files all over vendor/, and that makes dep check think all vendor folders have been changed.

I tried to check issues related to this but didn't find anything relevant (#286 mentioned bazel, but just in a broader spectrum as far as I understand). Does anyone know a good way of tackling this besides a delete all **/BUILD.bazel; run dep; run gazelle script?

I was wondering if something more granular than no-verify, like an exclude-files option, sounds reasonable / if a PR for it would be welcome.

@mvdan
Copy link
Member

mvdan commented Sep 4, 2020

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!

@mvdan mvdan closed this as completed Sep 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants