chavacava

I' ll close this issue. Feel free to reopen if you think the current behavior of the rule with `else-if` needs to be modified.

fixed by #862

Hi @yonderblue thanks for the proposal. My understanding of your proposal is: scoped disabling directives. Current implementation uses position (line numbers) of directives without scoping information. I'm afraid, making directive...

I'm not sure I understand the "splitting out into individual linters" idea. Anyway, if you are using `revive` through `golangci-lint` you can fully delegate the disabling/enabling of rules to `golangci-lint`...

Well I'm not a `golangci-lint` user. My understanding is that `golangci-lint` implements its own mechanism for enabling/disabling rules independent of that from underlying linters. You might ask on the `golangci-lint`...

Hi @echoix, thanks for filling the issue.

Hi @echoix, > I can make a PR with what I think should minimally work, that is, by porting the flags of the Makefile to the GoReleaser config. It sound...

Hi @echoix, any progress on the PR ?

Hi @marcelloh, thanks for reporting this issue. Could you please provide: 1. An example of _add in another file a comment not being a package comment_ 2. The actual failure...

Thanks. IMO the behavior of the rule is OK. The comment attached to the package declaration does not respect the conventions enforced by the rule. Must the rule warn in...