Ticket Cross Checker
Take gitlab issues and find them in code and vice versa. Create a mapping table to see what's covered, missing or wrong.
An example are the Gitlab Pages for this project.
Usage
start the cross checker in your CI pipeline
pages:
stage: test
script:
- pdm run discover ticket_cross_check spec
artifacts:
paths:
- public
rules:
- if: $CI_COMMIT_BRANCH == "main"
Add to existing gitlab pages
- caches existing
publicdirectories and creates a sub-dirtcc
cache:
paths:
- public
discover_issues:
image: python:latest
stage: build
script:
- python -m pip install --upgrade pip
- pip install ticket_cross_check
- discover code doc spec test -o public/tcc
artifacts:
paths:
- public
rules:
- if: $CI_COMMIT_BRANCH == "main"
Avoid logging
- we use loguru,
you can disable loguru auto init by setting
LOGURU_AUTOINITtoFalsein your environment
Development
Requirements
-
We use
pdmfor packaging (not pip, poetry or alinke) -
pdm installshall be run before you do anything (esp. in PyCharm), after that you find a.venvin the project root -
pdm add [-d] <package>to add more deps (fount in pyproject.toml)
How to install pdm
- See pdm homepage
- Usually you run
curl -sSL https://raw.githubusercontent.com/pdm-project/pdm/main/install-pdm.py | python3 -
Run gitlab-runner locally for single target
- download/install the gitlab-runner for your system
- install docker
- run
gitlab-runner exec docker <target>targetcomes from .gitlab-ci.yml - done :)
- btw caching only works with an S3 backend, see docs
Testing with pytest
- we use pytest
Code style with flake8
- config is in .flake8
- details can be found in the flake8 docs
Local installation and experiements
pdm installalso installs the cli scripts, defined in ticket_cross_check/init.py or pyproject.toml- you can run
discover <dir> [<dir> [<dir>]]to cross-check the given directories
Metadata
Release files for ticket-cross-check 0.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ticket-cross-check-0.10.1.tar.gz | 17.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ticket_cross_check-0.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.3 kB
Release files / ticket-cross-check-0.10.1.tar.gz
| Download URL | ticket-cross-check-0.10.1.tar.gz |
|---|---|
| Size | 17.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba19416fd4db7d642392d455e7400eb05b1bc7fb6c3d38042c069727b3cb68df
|
|
BLAKE2b-256 checksum How to use checksums |
b9eeb2a10a6a13806eda6e2593760ad98cf830c410fe98212e862e91beaa8979
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.3 readme-renderer/35.0 requests/2.28.1 requests-toolbelt/0.9.1 urllib3/1.26.11 tqdm/4.64.0 importlib-metadata/4.12.0 keyring/23.7.0 rfc3986/2.0.0 colorama/0.4.5 CPython/3.11.0
|
Release files / ticket_cross_check-0.10.1-py3-none-any.whl
| Download URL | ticket_cross_check-0.10.1-py3-none-any.whl |
|---|---|
| Size | 21.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a74eff8262f5f90672c4b5640257327b3fc2f058611fe7a658d2a2c65804a40
|
|
BLAKE2b-256 checksum How to use checksums |
09a26a53b615ae751512c16965c153a53c5769e3d12a88e28cef288261dd93b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.3 readme-renderer/35.0 requests/2.28.1 requests-toolbelt/0.9.1 urllib3/1.26.11 tqdm/4.64.0 importlib-metadata/4.12.0 keyring/23.7.0 rfc3986/2.0.0 colorama/0.4.5 CPython/3.11.0
|
Security for ticket-cross-check 0.10.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.