Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Projects with poor .gitignore coverage cause problems in ~/.voom-repos/ #22

Open
abrooks opened this issue Feb 17, 2014 · 1 comment
Open
Labels

Comments

@abrooks
Copy link
Contributor

abrooks commented Feb 17, 2014

Some projects don't sufficiently exclude build side effects (such as artifacts landing in target/) in their .gitignore files. When this happens in projects in ~/.voom-repos/, it prevents being able to automatically build voom versioned artifacts for the given project until the user clears the offending state (such as via a git checkout . in the ~/.voom-repos/ project directory).

Likely, since voom owns the ~/.voom-repos/ subdirectories, we should force a git-clean before checking out new versions which will fix this problem.

@abrooks abrooks added the bug label Feb 17, 2014
@abrooks
Copy link
Contributor Author

abrooks commented Oct 3, 2015

A work around, particularly for badly behaved 3rd party projects might be to allow git ignore patterns to be specified in the voom metadata.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant