docs: add note about binary requirement for plugin #3468
Merged
Conversation
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
The binary releases aren't compatible with private linters. This commit adds a section in the new linters documentation that describes the requirements for private linters to work.
|
Hey, thank you for opening your first Pull Request ! |
|
|
|
When trying to add a new private linter to golangci-lint I encountered some unexpected hurdles. This PR intends to save time for other users trying to create new private linters by describing the requirements. Related discussions and issues: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The binary releases aren't compatible with private linters. This commit adds a section in the new linters documentation that describes the requirements for private linters to work.