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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ Reviewers check these before merging into **`dev`**:
88
88
89
89
- Docstrings follow the [NumPy style](https://numpydoc.readthedocs.io/en/latest/format.html).
90
90
- API docs are built with [pdoc](https://github.com/mitmproxy/pdoc) (`make docu`). The package landing page (`corems.__doc__`) includes `README.md` and `docs/user/installation.md` so install content uses the same pdoc styling as the API.
91
-
- Maintainers: before cutting a release, run package lint (`make lint`) as described in [RELEASE.md](./RELEASE.md). Dev tooling is installed via `pip install -e ".[dev]"`.
91
+
- Maintainers: before cutting a release, run `make lint` as described in [RELEASE.md](./RELEASE.md). That command **rewrites** package Python (`ruff format` + `ruff check --fix`). Do not run it on a feature branch unless you intend to commit the diff. Dev tooling is installed via `pip install -e ".[dev]"`.
Copy file name to clipboardExpand all lines: RELEASE.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Release when `dev` has a coherent set of changes ready for users (features, fixe
23
23
|`make minor`| Backwards-compatible new features |
24
24
|`make major`| Incompatible API changes |
25
25
26
-
Each of those updates version metadata (see `.bumpversion.cfg`) and regenerates docs via `make docu` (UML class diagrams via `make uml` / pyreverse + Graphviz, then pdoc). The install how-to source is `docs/user/installation.md`, included on the package landing page through `corems.__doc__`. Maintainers need the `dev` extra (`pylint`) and system Graphviz (`dot`) installed so `make uml` succeeds during a version bump.
26
+
Each of those updates version metadata (see `.bumpversion.cfg`) and regenerates docs via `make docu` (UML class diagrams via `make uml` / pyreverse + Graphviz, then pdoc). The install how-to source is `docs/user/installation.md`, included on the package landing page through `corems.__doc__`. Maintainers need the `dev` extra (`ruff` for `make lint`, `pylint` for `pyreverse` / `make uml`, `pdoc`, …) and system Graphviz (`dot`) so format and docs steps succeed during a version bump.
27
27
28
28
## Release steps (GitLab)
29
29
@@ -33,21 +33,21 @@ All release steps should be done on the `dev` branch and then merged into `maste
33
33
- Gitlab CI green on `dev`.
34
34
- Changelog or release notes drafted (these will be copied into the MR description and later into the release on GitHub).
35
35
- No open blockers for the intended version.
36
-
-**Lint the package** (advisory maintainer review; not a hard CI gate):
37
-
1. Activate the same environment you use for CoreMS development and install/update dev extras so `pylint` is available, e.g.:
36
+
-**Format and auto-fix the package** (release prep; not a hard CI gate). This **rewrites files**.
37
+
1. Activate the same environment you use for CoreMS development and install/update dev extras so `ruff` is available, e.g.:
38
38
```bash
39
39
pip install -e ".[dev]"
40
40
```
41
41
2. From the repo root run:
42
42
```bash
43
43
make lint
44
44
```
45
-
This runs `pylint`on `corems`with project config from`pyproject.toml` (high-volume legacy style noise disabled so the report is usable). Use the venv’s Python (activate the venv first, or `make lint PYTHON=.venv/bin/python`) so import resolution matches a real install.
46
-
3. Optional broader pass (tests and support scripts):
45
+
This runs `ruff format`then`ruff check --fix`on `corems`(config in`pyproject.toml`). Use the venv’s Python (activate the venv first, or `make lint PYTHON=.venv/bin/python`). The first run after ruff is introduced will produce a large diff; later releases should be small.
46
+
3. Optional broader pass (tests and support scripts; also rewrites):
47
47
```bash
48
48
make lint-all
49
49
```
50
-
4. Review the report: fix release-blocking issues you care about; residual warnings are OK for this step. Proceed when you are satisfied—the step does not require a perfect score or exit code 0.
50
+
4. Review `git diff` and commit the formatted/fixed files (a dedicated commit is fine, especially the first time). Findings that `--fix` cannot apply may remain and may make the commandexit non-zero; that does not block the release. Do not use `--unsafe-fixes`.
51
51
52
52
2. **Bump version on `dev` (or a short-lived release branch from `dev`)**
With `corems[dev]`, maintainers can run package lint via `make lint` (see [RELEASE.md](../../RELEASE.md)).
47
+
With `corems[dev]`, maintainers can format and auto-fix the package via `make lint`at release time (see [RELEASE.md](../../RELEASE.md)). That command rewrites files.
48
48
49
49
Check the installed package metadata or `pyproject.toml` for the current list of extras.
0 commit comments