-
-
GitHub Actions is easier to use and maintain. For example, GitHub Actions is more popular and widely used, and so more familiar. It's easier to maintain a single system. Also core devs can restart fai…
-
### Library name
N/A
### Please describe the feature.
Right now, any change in `./eng` apart from the excludes will trigger `net-core-ci`, which takes quite a while to finish.
https://github…
-
### What information needs to be added?
Currently, there is no documentation for GitHub Actions without using fastlane in the CI/CD documentation. Since not everyone is using fastlane, how about expl…
-
## Description
In the monorepo we encounter intermittent build failures on jobs that use the GitHub Action cache (mostly indirectly via actions like `setup-java`, etc) with error messages like `Err…
-
I'd love to take a PR for this if anyone wants to take this on.
-
CI fails:
- pre-commit, because of unlinted or differently linted source checked in. When the source is updated for things like 'trimmed trailing whitespace"
- pytest fails. No tests are written y…
-
#### Objective:
Create CI (Continuous Integration) files for GitHub and GitLab that include the basic steps for running code quality and security checks in an Elixir project.
#### Basic Steps to R…
-
Now that we have a minimal `test.py` file, we can setup a Github actions CI to run it with every PR and push to main.
-
What will be reasonable to test, either on periodic basis or maybe on GLVis push?
See https://github.com/GLVis/glvis/issues/124