You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When adding revive to large, complex workflows such as linter suites or CI/CD jobs, then there is a reasonable expectation that the tool provides meaningful exit codes by default.
Describe the solution you'd like
Enable -set_exit_status by default.
Describe alternatives you've considered
Copying and pasting the -set_exit_status flag everywhere is cumbersome and unintuitive.
Copying configuration files everywhere is also somewhat cumbersome and unintuitive.
Additional context
Somewhat of a breaking change, in case engineers are already running revive in their CI/CD pipelines. As a precaution, this change would be a good time to cut a new major version, 2.0.0. We can use SemVer to help communicate the new default behavior.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When adding revive to large, complex workflows such as linter suites or CI/CD jobs, then there is a reasonable expectation that the tool provides meaningful exit codes by default.
Describe the solution you'd like
Enable
-set_exit_status
by default.Describe alternatives you've considered
-set_exit_status
flag everywhere is cumbersome and unintuitive.Additional context
Somewhat of a breaking change, in case engineers are already running revive in their CI/CD pipelines. As a precaution, this change would be a good time to cut a new major version, 2.0.0. We can use SemVer to help communicate the new default behavior.
The text was updated successfully, but these errors were encountered: