gno
Interactive CLI tool for building .gitignore files
gno (pronounced "noh") helps you create .gitignore files interactively with a beautiful split-pane TUI interface. It fetches templates from GitHub's official gitignore repository and caches them locally for fast access.
Features
- Interactive TUI - Split-pane interface with live preview
- 230+ Templates - All templates from GitHub's gitignore repository
- Smart Search - Filter templates by name or description
- Smart Merging - Append to existing files without duplicates
- Offline Support - Templates cached locally after first fetch
- Multiple Output Modes - Interactive, generate, preview
Installation
# Using uv (recommended)
uv tool install gno
# Or run directly without installing
uvx gno
# Using pipx
pipx install gno
# Using pip
pip install gno
Usage
Interactive Mode
Launch the TUI by running gno without arguments:
gno
Controls:
Up/Downorj/k- Navigate templatesSpace- Toggle selection/- Search templatess- Save and exit?- Show helpq- Quit
Command Line
# Generate .gitignore from templates
gno generate python node
# Preview without saving
gno generate python --preview
# Save to custom path
gno generate rust -o backend/.gitignore
# Append to existing file (smart merge)
gno generate go --append
# List all templates
gno list
# Search templates
gno list python
# Show template content
gno show python
# Update template cache
gno update
Examples
Create a Python project .gitignore
gno generate python
Create a full-stack project .gitignore
gno generate python node
Add templates to existing .gitignore
gno generate terraform --append
Template Sources
Templates are fetched from:
- github/gitignore - Root directory (language templates)
- github/gitignore/Global - Global templates (editors, OS, etc.)
- github/gitignore/community - Community templates (community-contributed templates)
Cache
Templates are cached in ~/.gno/templates.json for offline access and faster startup. Run gno update to refresh the cache.
Development
# Clone the repository
git clone https://github.com/OseSem/gno
cd gno
# Install dependencies
uv sync
# Run the CLI
uv run gno
# Run tests
uv run pytest
# Run linting
uv run ruff check .
uv run black --check .
License
MIT License - see LICENSE for details.
Metadata
Release files for gno 0.1.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 | |
|---|---|---|---|
| gno-0.1.1.tar.gz | 14.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gno-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.1 kB
Release files / gno-0.1.1.tar.gz
| Download URL | gno-0.1.1.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08fc03eeb071e0f8ab037878695ebcfb7d7bbad1227ac1d675792dc00b24f8e8
|
|
BLAKE2b-256 checksum How to use checksums |
902743f457c5ef720e832455071ec8f50d034f94986cfe9fcd103fc55104c038
|
| 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 Feb 5, 2026.
Transparency logRelease files / gno-0.1.1-py3-none-any.whl
| Download URL | gno-0.1.1-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d58bd7c95f48cf5a2450feca4eaf9f9a8fa620362dcefa9a885004732d24f6f8
|
|
BLAKE2b-256 checksum How to use checksums |
3909b5e5d4b1a6b63fc5f97bb78a8ac2009b9e5f2f5dcb8074281f4c150733ea
|
| 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 Feb 5, 2026.
Transparency log