Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
53 changes: 0 additions & 53 deletions .github/workflows/docker.yaml

This file was deleted.

45 changes: 0 additions & 45 deletions .github/workflows/main.yaml

This file was deleted.

1 change: 0 additions & 1 deletion .github/workflows/rbs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,5 @@ concurrency:
jobs:
build-test:
uses: ReduxISU/Redux_Build_System/.github/workflows/ci.yml@main
with: { dry-run: true }
secrets: inherit

17 changes: 16 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
[![build and unit tests](https://github.com/ReduxISU/quantumsolver/actions/workflows/main.yaml/badge.svg)](https://github.com/ReduxISU/quantumsolver/actions/workflows/main.yaml)
[![rbs](https://github.com/ReduxISU/quantumsolver/actions/workflows/rbs.yml/badge.svg)](https://github.com/ReduxISU/quantumsolver/actions/workflows/rbs.yml)

This is a flask application that will integrates with [Redux](https://github.com/ReduxISU/Redux) to provide qiskit based solvers
for problems.
Expand Down Expand Up @@ -56,6 +56,21 @@ uv run ruff check .
uv run black --check .
```

## CI and publishing

One workflow, `.github/workflows/rbs.yml`, runs the whole pipeline through the
[Redux Build System](https://github.com/ReduxISU/Redux_Build_System) inside this repo's devcontainer:
`audit → format-check → lint → unit-test (3.12, 3.13) → build → integration-test → push`. Gates and
thresholds live in `rbs.toml`. The same command runs locally:

```
rbs ci
```

On a push to `main`, and only if every gate passed, `push` publishes the exact image the
integration tests ran against to `ghcr.io/reduxisu/quantumsolver` as `:<sha7>` and `:latest`. On
pull requests it reports `skipped`.

## API Endpoints

All solver endpoints accept `POST` with a JSON body and return a JSON object containing at minimum an `"answer"` field and a `"qasm"` field with the generated circuit.
Expand Down
Loading