-
### Describe the bug
CI links:
https://github.com/valkey-io/valkey-glide/actions/runs/11698386348/job/32578606911#step:6:57
https://github.com/valkey-io/valkey-glide/actions/runs/11698386348/job/…
-
### Describe the enhancement requested
There is currently a single CI job on appveyor. This is the only job on Windows for Python and it usually fails due to CI issues rather than Python real issues.…
-
If we want to see new builds this would have to be ported from Travis CI to GItHub Actions.
Volunteers?
-
**Please describe your new feature request**
It would be good to see the library and example projects compilation, test and lint checks results when submitting and reviewing PRs.
**Describe the …
-
**Describe the bug**
It works in local environment.
Error in actions CI/CD deployment
I watch this.
but I couldn't avoid the error.
https://github.com/Azure/static-web-apps/issues/531
```
…
-
**As a developer** I need a reliable, scalable CI solution well integrated with GitHub. Actions seems a natural choice.
# Acceptance criteria
- All CI checks successfully run with GitHub actions…
-
As the TravisCI API seems to have changed so that the build status doesn't work anymore:
…
-
### Package version
3.0.0
### Describe the bug
When attempting to run `npm ci` or `npm ci --production` on aws or github actions it fails saying the `package-lock.json` does not match the `p…
-
These jobs are still using azp and require a ~local cache setup before they can be moved (#32469)
Once these jobs move it will hugely increase Engflow usage
-
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.