@@ -11,6 +11,10 @@ used on any POSIX-compliant system.
1111
1212See ` overview.md ` for further details.
1313
14+ ## Development workflow
15+
16+ ### Build
17+
1418Developer's workflow using ` micromamba ` to manage the dependencies:
1519
1620``` bash
@@ -23,19 +27,31 @@ make -j8
2327
2428The ` git2cpp ` executable can then be run, e.g. ` ./git2cpp -v ` .
2529
30+ ### Test
31+
2632The CLI is tested using ` python ` . From the top-level directory:
2733
2834``` bash
2935pytest -v
3036```
3137
38+ Some tests access the private repository at https://github.com/QuantStack/git2cpp-test-private using
39+ a fine-grained github Personal Access Token (PAT). These tests are skipped by default. To run them
40+ you will need to obtain the PAT from one of the maintainers, and run the tests as follows:
41+
42+ ``` bash
43+ GIT2CPP_TEST_PRIVATE_TOKEN=< this-is-the-personal-access-token> pytest -v
44+ ```
45+
46+ ### pre-commit
47+
3248` pre-commit ` runs automatically on ` git commit ` . To run it manually use:
3349
3450``` bash
3551pre-commit run --all-files
3652```
3753
38- # WebAssembly build and deployment
54+ ## WebAssembly build and deployment
3955
4056The ` wasm ` directory contains everything needed to build the local ` git2cpp ` source code as an
4157WebAssembly [ Emscripten-forge] ( https://emscripten-forge.org/ ) package, create local
@@ -48,7 +64,7 @@ See the `README.md` in the `wasm` directory for further details.
4864The latest ` cockle ` and JupyterLite ` terminal ` deployments using ` git2cpp ` are available at
4965[ https://quantstack.net/git2cpp ] ( https://quantstack.net/git2cpp )
5066
51- # Documentation
67+ ## Documentation
5268
5369The project documentation is generated from the ` git2cpp ` help pages. To build the documentation
5470locally first build ` git2cpp ` as usual as described above, then install the documentation
0 commit comments