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,556 public repositories matching this topic...
-
Updated
Jul 22, 2021 - Go
-
Updated
Jul 8, 2021 - JavaScript
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
-
Updated
Jul 23, 2021 - Java
Garden supports disabling privileged containers, and some users have configured it (see Discord message) - should we support that for the containerd
runtime too?
-
Updated
Jul 23, 2021 - JavaScript
JanitorConfigurator
should have an option to delete logs for specific builders (or tags). Users might want to delete logs for only specific builders, or might want to keep logs for specific builders for longer duration.
http://docs.buildbot.net/latest/manual/cfg-configurators.html#janitorconfigurator currently doesn't seems to contain any such option.
-
Updated
Jul 20, 2021 - Swift
-
Updated
Jul 22, 2021 - Ruby
-
Updated
Jun 30, 2021 - TypeScript
Many repositories need to fix, so please help if you like.
If you could help, it would be helpful if you could comment before starting the work not to overlapping.
Fix example
Run exit command after lint.
echo '::group:: Running golangci-lint with reviewdog 🐶 ...'
go
-
Updated
Jul 23, 2021 - Go
-
Updated
Apr 27, 2021
-
Updated
Jul 7, 2020 - JavaScript
Export headers are nice.
-
Updated
Jul 12, 2021 - Go
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
-
Updated
Dec 18, 2020 - Go
-
Updated
Jul 16, 2021 - Go
-
Updated
Jul 22, 2021 - Java
-
Updated
May 20, 2021 - Shell
-
Updated
Jul 23, 2021 - Dockerfile
- Wikipedia
- Wikipedia
Config:
Input: