Skip to main content

Git Configurator ⚙️✨

GitHub Sponsors Patreon Buy Me a Coffee PayPal

Git Configurator is a Python-based utility that simplifies setting up your global Git configuration. It interactively guides you through selecting merge strategies, setting author details (including website), and choosing your commit signing preferences. Alternatively, you can configure everything via command-line arguments for automated setup.

Features 🚀

  • Interactive Setup:
    Follow step-by-step prompts to configure merge options, author name/email, website, and GPG signing settings.
  • Non-Interactive Mode:
    Use command-line arguments for quick, automated configuration.
  • Global Git Configuration:
    Easily set up your Git environment with a single command.
  • Integration with Kevin's Package-Manager:
    Installable via Kevin's Package-Manager under the alias gitconfig for global access.

Installation 📦

You can run the script directly:

python3 main.py --interactive

Or, if you have Kevin Package-Manager installed, install Git Configurator with:

pkgmgr install git-configurator

Then, use it globally via:

gitconfig --help

Usage 💻

  • Interactive Mode:

    gitconfig --interactive
    

    Follow the on-screen prompts to set your Git configuration.

  • Non-Interactive Mode:

    gitconfig --merge-option rebase --name "John Doe" --email "john@example.com" --website "https://johndoe.com" --signing gpg --gpg-key YOUR_GPG_KEY
    

🔑 Using Your GPG Key with Git Configurator

To sign your Git commits with a GPG key, you must first identify your key ID. Follow these steps to find your GPG key ID:

1. List your available GPG keys:

gpg --list-secret-keys --keyid-format LONG

You will see output similar to:

/home/youruser/.gnupg/pubring.kbx
--------------------------------------------
sec   rsa4096/A1B2C3D4E5F6G7H8 2020-12-29 [SC]
      1234ABCD5678EFGH9012IJKL3456MNOP7890QRST
uid                 [ultimate] John Doe <john@example.com>
ssb   rsa4096/Z9Y8X7W6V5U4T3S2 2020-12-29 [E]

The GPG key ID you need for Git configuration is the short form displayed after rsa4096/, in this example:

A1B2C3D4E5F6G7H8

2. Configure your GPG key with Git Configurator:

gitconfig --signing gpg --gpg-key R5T6Y7U8I9O0P1Q2

Replace R5T6Y7U8I9O0P1Q2 with your actual key ID from the output above.

License 📄

This project is licensed under the MIT License.

Author 👤

Kevin Veen-Birkenbach
veen.world

Acknowledgements 🤖💡

This script was created with the help of ChatGPT.


Happy configuring! 🎉

Metadata

Release files for gitcon 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gitcon 1.0.0
File Size Uploaded
gitcon-1.0.0.tar.gz 8.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for gitcon 1.0.0
File Interpreter ABI Platform
gitcon-1.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 12.6 kB

Release files / gitcon-1.0.0.tar.gz

Download URL gitcon-1.0.0.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
38ca6e4061efdae5b91295efd9b5ac048b73e678b8079510e4fb38916ebc0706
BLAKE2b-256 checksum
How to use checksums
1b272511c2ef6ebf28aba3f9b262d5bc1a3c2b3929b58b0a34d79207a8a611e8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 13, 2025.

Transparency log

Release files / gitcon-1.0.0-py3-none-any.whl

Download URL gitcon-1.0.0-py3-none-any.whl
Size 4.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2c5cb147e5c2790fd6cf50946808c65c42719c077518b0310cbc764157ed29f0
BLAKE2b-256 checksum
How to use checksums
5f5b0a4d473ae21b796ec74839bd9e9813d470ab256e50f0d4e0e3a192d1ffbc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Dec 13, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page