-
I want to enforce a system where any new branch must be reviewed, and all test cases must pass before code can be merged onto main. I also would like to have some sort of system in place to assist any…
-
See discussion in https://github.com/mwpenny/portal64-still-alive/pull/47#issuecomment-2080446622.
It would be easier to avoid breaking the build by implementing CI builds. For example, using GitHu…
-
As of now, we're not running linting and tests as part of CI for this repo. They do run locally and have E2E tests too.
-
(cc @connor4312)
In vscode-jest, we have started integrating the `autoRun` feature with VSCode's Continuous Testing API and have encountered a few issues that I hope you can help us resol…
-
Needs for CI:
- [X] Checking validity of internal links without anchors (#240)
- [ ] Checking validity of internal links with anchors
- [ ] Checking validity of external links (see: https://pypi.…
-
We added MOSEK to the list of supported solvers last year in https://github.com/qpsolvers/qpsolvers/pull/212 (see also https://github.com/qpsolvers/qpsolvers/issues/211). The license shared by MOSEK h…
-
## Goal
If we want make PyRenew widely usable, we should extend our CI to run across multiple platforms and ensure that our code works as expected.
## Context
While working through our tutori…
-
-
##### Expected Behavior
LxQT components are tested on all platforms after each PR/commit
##### Current Behavior
I do not see anything like that
##### Possible Solution
Integrate…
-
@erictheise to add details to what is included here. Idea is to pull in upstream regularly, run tests, merge, deploy ongoing.