git-dct
Git development CLI tools for daily usage
Documentation: https://radiandevcore.gitlab.io/tools/git-dct
Package: https://pypi.org/project/git-dct/
Usage
usage: git-dct [-h] [--version] [--no-color] [--update-check] [--settings] [--set GROUP KEY VAL] [-e | -d] [--]
git-dct: Git development CLI tools for daily usage
internal arguments:
-h, --help # Show this help message
--version # Show the current version
--no-color # Disable colors outputs with 'NO_COLOR=1'
# (or default settings: [themes] > no_color)
--update-check # Check for newer package updates
--settings # Show the current settings path and contents
--set GROUP KEY VAL # Set settings specific 'VAL' value to [GROUP] > KEY
# or unset by using 'UNSET' as 'VAL'
modes arguments:
-e, --enable # Enable profiles configurations
-d, --disable # Disable profiles configurations
positional arguments:
-- # Positional arguments separator (recommended)
Enable Git configurations
git dct --enable
Disable Git configurations
git dct --disable
Userspace available settings
git-dct creates a settings.ini configuration file in a userspace folder.
For example, it allows to disable the automated updates daily check ([updates] > enabled)
The settings.ini file location and contents can be shown with the following command:
git-dct --settings
Environment available configurations
git-dct uses colored for colors outputs and questionary for interactive menus.
If colors of both outputs types do not match the terminal's theme,
an environment variable NO_COLOR=1 can be defined to disable colors.
Dependencies
- colored: Terminal colors and styles
- questionary: Interactive terminal user interfaces
- setuptools: Build and manage Python packages
- update-checker: Check for package updates on PyPI
References
- commitizen: Simple commit conventions for internet citizens
- git-cliff: CHANGELOG generator
- gitlab-release: Utility for publishing on GitLab
- gcil: Launch .gitlab-ci.yml jobs locally
- mkdocs: Project documentation with Markdown
- mkdocs-coverage: Coverage plugin for mkdocs documentation
- mkdocs-exporter: Exporter plugin for mkdocs documentation
- mkdocs-material: Material theme for mkdocs documentation
- mypy: Optional static typing for Python
- pre-commit: A framework for managing and maintaining pre-commit hooks
- pre-commit-crocodile: Git hooks intended for developers using pre-commit
- PyPI: The Python Package Index
- twine: Utility for publishing on PyPI
Metadata
Release files for git-dct 5.0.0
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 | Actions |
|---|---|---|---|---|
| git_dct-5.0.0.tar.gz | 91.1 kB | Without provenance | Details for git_dct-5.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| git_dct-5.0.0-py3-none-any.whl | Python 3 | none | any | Details for git_dct-5.0.0-py3-none-any.whl |
Total release size: 140.0 kB
Release files / git_dct-5.0.0.tar.gz
| Download URL | git_dct-5.0.0.tar.gz |
|---|---|
| Size | 91.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0dba3d70d75689ad6d67e099fb4b5b019ce212e6fa7a7e98acba17fc66e56363
|
|
BLAKE2b-256 checksum How to use checksums |
4f8a67a09a65b5416e69670ac4044a08678071a464abff5503620151bb7ad83c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Release files / git_dct-5.0.0-py3-none-any.whl
| Download URL | git_dct-5.0.0-py3-none-any.whl |
|---|---|
| Size | 49.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c19425fe913e6a8b09db3322b5ff9419c0a5ec372cc311add902dfa510c22b7f
|
|
BLAKE2b-256 checksum How to use checksums |
258b45397f83f339d71c8d013eaef6ffe3106b7ff764cd8519163930b3f0873d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Security for git-dct 5.0.0
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.