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

Link to documentation on how to resolve a conflict #2155

merged 1 commit into from Feb 25, 2017


None yet
2 participants

0x53A commented Feb 25, 2017

When I got this error (due to a broken package), it took me way too long to find the correct documentation.

I'm a big fan of error messages telling you what to do.

(I didn't mention the == operator directly in the error message on purpose, because fixing the version can cause a lot of fun ( MethodNotFoundException <3 ), and there should be at least a chance to warn the user.

What would you think about adding a big bold warning to how it can cause all kinds of trouble? (Here be dragons ...)


This comment has been minimized.

Show comment
Hide comment

forki Feb 25, 2017




forki commented Feb 25, 2017


@forki forki merged commit 754bfc0 into fsprojects:master Feb 25, 2017

0 of 2 checks passed

continuous-integration/appveyor/pr AppVeyor build failed
continuous-integration/travis-ci/pr The Travis CI build failed

@0x53A 0x53A deleted the 0x53A:patch-1 branch Apr 16, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment