Open
Conversation
Member
|
While I do agree we should propose the simplest options up front, I don't think we can necessarily get away from needing to merge in some circumstances. Also, moving to a So while it may solve 1 CI specific issue, I think it causes bigger projects to not want to run analyzers locally if the solution is the only option documented. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To fix my problem in #243, I concluded that running everything in a single pass is the most convenient option. You can do that with a single solution target.
FSharp.Analyzers.Buildmay have been overly complicated to start with. I updated the documentation and am proposing this simpler approach.Let me know what you think.