-
Notifications
You must be signed in to change notification settings - Fork 231
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
chore(ci): add golangci-lint action and apply linting changes #120
Conversation
Pull Request Test Coverage Report for Build 658991180
💛 - Coveralls |
Type string // (e.g. `feat`) | ||
Scope string // (e.g. `core`) | ||
Subject string // (e.g. `Add new feature`) | ||
JiraIssueID string // (e.g. `RNWY-310`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a BREAKING CHANGE
as the original role out of the Jira integration expected JiraIssueId
as the type in the config.
Thank you @clok for taking the initiative! I personally would like to suggest even more enhancement (collapsed for brevity). content of
|
And please don't hesitate to let me know to give a hand for fixing these. I didn't already do it to prevent stepping on your toes. |
@khos2ow Appreciate it! Just an FYI - no need to worry about stepping on my toes. Always appreciate a collaborative effort on coding. I just recommend communicating one's intentions to the team just so that way we don't have duplicated efforts. I really appreciate the more detailed and thorough configuration. I am going to take some time to look it over. For now, if you want to take a pass at addressing these issues, please do so. I won't be able to focus on this until later this evening. Thank you again for the collaboration! I'll keep an eye for any changes that may be pushed before taking on any other actions when I come back around to this. |
Awesome, then I will commit the configuration just now, and will attempt to fix as much as I can a little while later. |
Signed-off-by: Khosrow Moossavi <khos2ow@gmail.com>
I also removed myself from reviewers, as it doesn't make sense for me to be reviewing my own work! 😅 |
Signed-off-by: Khosrow Moossavi <khos2ow@gmail.com>
Signed-off-by: Khosrow Moossavi <khos2ow@gmail.com>
@khos2ow thank you for the updates. I pushed a few other patches to address The We still have |
Signed-off-by: Khosrow Moossavi <khos2ow@gmail.com>
@clok I think the best approach for dealing with On the other hand |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
I agree the gocyclo
can be tackled later in separate issues. Feel free to open them, so we keep track. The BC is also fine. As the naming will be caught in the future and we are still pre-major.
@khos2ow I like that approach. Thank you for putting the comments and Unless you feel we can take care of the @mavogel Roger that on the BC. |
chglog.go
Outdated
scopeErr := back() | ||
if scopeErr != nil { | ||
log.Fatal(scopeErr) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also can be written as
if err = back(); err != nil {
log.Fatal(err)
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like that. I always forget the inline boolean check.
What does this do / why do we need it?
This adds linting and formatting expectations to the project. Linting allows for code written and maintained by a group of individuals to read as if it comes from one collective mind. This helps with maintainability, readability and other "bility" words.
How this PR fixes the problem?
It adds the
golangci-lint
project as a Development and CI dependency. It uses the linters that are enabled by default as well as:What should your reviewer look out for in this PR?
These are linters that I have used in the past. I have found them helpful, but I would like the opinions of others.
Each commit contains the delta required to pass a given linter.
Check lists
Additional Comments (if any)
For reference, here was the

golangci-lint
output before these changes:Which issue(s) does this PR fix?
fixes #89