You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This package implements different workflows for CI.
4
-
They are organised as follows.
4
+
They are organized as follows.
5
5
6
6
### Documentation
7
7
@@ -12,12 +12,12 @@ It runs on `ubuntu-latest` and one of our supported version, currently `Python 3
12
12
13
13
Tests are ensured in the `tests` workflow, in two stages.
14
14
The first stage runs our simple tests on all push events (except to `master`), and the second one runs the rest of the testing suite (the `extended` tests).
15
-
Tests run on a matrix of all supported operating systems (ubuntu-20.04, ubuntu-22.04,windows-latest and macos-latest) for all supported Python versions (currently `3.8`, `3.9`, `3.10` and`3.11`).
15
+
Tests run on a matrix of all supported operating systems (`ubuntu-20.04`, `ubuntu-22.04`, `windows-latest` and `macos-latest`) for all supported Python versions (currently `3.8` to`3.11`).
16
16
17
17
### Test Coverage
18
18
19
-
Test coverage is calculated in the `coverage`wokflow, which triggers on pushes to `master` and any push to a `pull request`.
20
-
It runs on `ubuntu-latest` and one of our supported version, currently `Python 3.9`, and reports the coverage results of the test suite to `CodeClimate`.
19
+
Test coverage is calculated in the `coverage`workflow, which triggers on pushes to `master` and any push to a `pull request`.
20
+
It runs on `ubuntu-latest` and `Python 3.9`, and reports the coverage results of the test suite to `CodeClimate`.
21
21
22
22
### Regular Testing
23
23
@@ -26,5 +26,5 @@ It also runs on `Python 3.x` so that newly released Python versions that would b
26
26
27
27
### Publishing
28
28
29
-
Publishing to `PyPI` is done through the `publish` workflow, which triggers anytime a `release` is made of the Github repository.
29
+
Publishing to `PyPI` is done through the `publish` workflow, which triggers anytime a `release` is made of the GitHub repository.
30
30
It builds a `wheel`, checks it, and pushes to `PyPI` if checks are successful.
0 commit comments