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,417 public repositories matching this topic...

golangci-lint
MrWormHole
MrWormHole commented May 7, 2021

Is your feature request related to a problem? Please describe.
I am disappointed by not seeing all integration options on the introduction page because emacs, vscode and sublime are the only listed ones. It could save me a lot of time if I checked it out integrations page(which is quite extensive and super great) first instead of going over intro and quick start

**Describe the solution you

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

vito
vito commented Feb 3, 2021

Summary

#6369 tracks the user who created the build (either manual trigger or rerun) and also tweaked the api/v1/user endpoint to contain a new display_user_id field. The new field should be used to show the user in the top bar, since it reflects the same value that Concourse tracks as the build creator.

We should be able to replace [this function](https://github.com/concourse/concour

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

Wikipedia
Wikipedia