Skip to content
#

ci

Automatically build and test your code as you push it upstream, preventing bugs from being deployed to production. A complementary practice to CI is that before submitting work, each programmer must do a complete build and run (and pass) all unit tests. Integration tests are usually run automatically on a CI server when it detects a new commit.

Here are 3,876 public repositories matching this topic...

golangci-lint
mykter
mykter commented Aug 19, 2021

Your feature request related to a problem? Please describe.

GoKart is a new stand-alone security-focused static analysis tool.

Describe the solution you'd like.

Add support for GoKart. It uses go/analysis.

Describe alternatives you've considered.

Run GoKart separately to golangci-lint.

Additional context.

_No respo

dec5e
dec5e commented Jan 28, 2021

Describe the bug

git diff-tree used by linter on push checks only files from the last commit and regardless of files status, so deleted or renamed files are also checked.

There are now 2 different git commands used for finding the list of broken files (find them here: https://github.com/github/super-linter/blob/v3.14.4/lib/functions/buildFileList.sh#L59-L105). git diff-tree is u

reviewdog
Mocky
moniuch
moniuch commented Apr 25, 2017

I would welcome a feature when, at the same url which is set to respond with OK status, I could have an error response generated with a random seed.

I am developing an Observable pattern to perform a series of retries to call an endpoint, with increasing delay. The problem is that during testing, I cannot really mock up the condition by randomly switching between two mocky.io urls (error and ok

flagsmith
Wikipedia
Wikipedia