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,241 public repositories matching this topic...
-
Updated
Feb 7, 2021 - Go
-
Updated
Jan 1, 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
Feb 5, 2021 - Java
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
-
Updated
Feb 7, 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
Feb 2, 2021 - Ruby
-
Updated
Feb 4, 2021 - Swift
-
Updated
Feb 5, 2021 - TypeScript
-
Updated
Feb 7, 2021 - Go
-
Updated
Dec 8, 2020
-
Updated
Jul 7, 2020 - JavaScript
Describe the bug
GEN003 is triggering for the name of a secret in a github_actions_organization_secret resource. Going off the documentation for GEN003, it should only be triggering for secret VALUES, and not secret NAMES.
To Reproduce
variable "value"-
Updated
Feb 7, 2021 - CMake
-
Updated
Feb 4, 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
Jan 23, 2021 - Go
-
Updated
Feb 3, 2021 - Python
-
Updated
Jan 2, 2021 - Rust
-
Updated
Jan 15, 2021 - Python
-
Updated
Oct 17, 2019 - Go
- Wikipedia
- Wikipedia
Config:
Input: