-
Notifications
You must be signed in to change notification settings - Fork 949
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
docs: user general pouchlinter to linter pouch's code #2421
docs: user general pouchlinter to linter pouch's code #2421
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2421 +/- ##
==========================================
+ Coverage 64.07% 68.61% +4.53%
==========================================
Files 275 275
Lines 18309 18309
==========================================
+ Hits 11731 12562 +831
+ Misses 5292 4327 -965
- Partials 1286 1420 +134
|
f98b70d
to
ddb1434
Compare
Signed-off-by: Allen Sun <[email protected]>
ddb1434
to
04037f7
Compare
The gometalinter works. @fuweid |
Some scripts are used to help developer to install dependences easier. I think we can keep it. |
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.
LGTM
command: make check | ||
name: validate go code with gometalinter | ||
command: | | ||
gometalinter --disable-all --skip vendor -E gofmt -E goimports -E golint -E ineffassign -E misspell -E vet -E megacheck ./... |
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.
one more question, could we just use make check
here, since the image provides the binary?
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 think both are OK, while if we use make check
, the calling path is a little bit long. For the test part and ci part, in my opinion, simplicity is the most important thing.
Signed-off-by: Allen Sun [email protected]
Ⅰ. Describe what this PR did
user general pouchlinter to linter pouch's code.
For more info about pouchlinter, please check https://github.com/pouchcontainer/pouchlinter
The doc change in test.md and pouch_with_plugin.md is according to markdowinlint rule https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md#md046---code-block-style .
Ⅱ. Does this pull request fix one issue?
none
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗?)
no need
Ⅳ. Describe how to verify it
none
Ⅴ. Special notes for reviews
none