uv-forger 0.1.0__tar.gz

uv_forger-0.1.0/.github/DISCUSSION_TEMPLATE/q-a.yml

@@ -0,0 +1,60 @@
+title: "[Question] "
+labels: ["question"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your question! To help me give you the best answer, please fill out the sections below.
+
+  - type: textarea
+    id: question
+    attributes:
+      label: Your Question
+      description: What would you like to know? Be as specific as you can.
+      placeholder: "e.g. Why does my function return None instead of the list I expected?"
+    validations:
+      required: true
+
+  - type: textarea
+    id: code
+    attributes:
+      label: Your Code
+      description: Please paste the relevant Python code below. This is the most important thing I need to help you!
+      render: python
+      placeholder: |
+        def my_function():
+            # paste your code here
+            pass
+    validations:
+      required: true
+
+  - type: textarea
+    id: error
+    attributes:
+      label: Error Message or Unexpected Output
+      description: If you're seeing an error, paste the full traceback here. If the output is just wrong, describe what you expected vs. what you got.
+      render: shell
+      placeholder: |
+        Traceback (most recent call last):
+          ...
+        TypeError: ...
+    validations:
+      required: false
+
+  - type: textarea
+    id: tried
+    attributes:
+      label: What Have You Already Tried?
+      description: Share anything you've already attempted — it helps avoid suggestions you've already ruled out.
+      placeholder: "e.g. I tried changing X to Y but got the same result."
+    validations:
+      required: false
+
+  - type: input
+    id: python-version
+    attributes:
+      label: Python Version
+      description: What version of Python are you using? (Run `python --version` to check.)
+      placeholder: "e.g. 3.12.2"
+    validations:
+      required: false

uv_forger-0.1.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,81 @@
+name: Bug Report
+description: Something isn't working as expected
+title: "[Bug] "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug! The more detail you can provide, the easier it is to track down.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: What happened?
+      description: A clear description of what the bug is.
+      placeholder: "e.g. The function returns None instead of the expected list."
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: What did you expect to happen?
+      placeholder: "e.g. I expected the function to return a sorted list of strings."
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: How can I reproduce the issue?
+      placeholder: |
+        1. Run ...
+        2. Call function with ...
+        3. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: code
+    attributes:
+      label: Relevant Code
+      description: Paste any relevant Python code here.
+      render: python
+      placeholder: |
+        def my_function():
+            # paste your code here
+            pass
+    validations:
+      required: false
+
+  - type: textarea
+    id: error
+    attributes:
+      label: Error Message or Traceback
+      description: If you're seeing an error, paste the full traceback here.
+      render: shell
+      placeholder: |
+        Traceback (most recent call last):
+          ...
+        TypeError: ...
+    validations:
+      required: false
+
+  - type: input
+    id: python-version
+    attributes:
+      label: Python Version
+      description: What version of Python are you using? (Run `python --version` to check.)
+      placeholder: "e.g. 3.12.2"
+    validations:
+      required: false
+
+  - type: input
+    id: os
+    attributes:
+      label: Operating System
+      placeholder: "e.g. Windows 11, macOS 14, Ubuntu 22.04"
+    validations:
+      required: false

uv_forger-0.1.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,44 @@
+name: Feature Request
+description: Suggest an idea or improvement for this project
+title: "[Feature] "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the suggestion! Please fill out the sections below to help me understand what you have in mind.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem does this solve?
+      description: Is your feature request related to a problem or limitation you've run into?
+      placeholder: "e.g. I find it frustrating when I have to manually do X every time..."
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you'd like
+      description: What would you like to see added or changed?
+      placeholder: "e.g. It would be helpful if the project could automatically handle X by doing Y."
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives you've considered
+      description: Have you tried any workarounds or other approaches?
+      placeholder: "e.g. I tried using library Z but it doesn't quite fit because..."
+    validations:
+      required: false
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Anything else that might help — examples, links, screenshots, etc.
+    validations:
+      required: false

uv_forger-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,27 @@
+## Summary
+
+<!-- Brief description of what this PR does and why. -->
+
+## Changes
+
+<!-- Bullet list of key changes. -->
+
+-
+
+## Related Issues
+
+<!-- Link any related issues: Fixes #123, Closes #456, Related to #789 -->
+
+## Testing
+
+<!-- How were these changes tested? -->
+
+- [ ] Existing tests pass (`uv run pytest`)
+- [ ] New tests added (if applicable)
+- [ ] Manual testing done
+
+## Checklist
+
+- [ ] Code follows project conventions
+- [ ] Linting passes (`uv run ruff check uv_forge`)
+- [ ] No new warnings introduced

uv_forger-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,30 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv run ruff check uv_forge
+      - run: uv run ruff format --check uv_forge
+
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        python-version: ["3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: uv sync --dev
+      - run: uv run pytest -q --tb=short

uv_forger-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,17 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv build
+      - uses: pypa/gh-action-pypi-publish@release/v1

uv_forger-0.1.0/.gitignore

@@ -0,0 +1,43 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+
+# Test coverage reports
+htmlcov/
+.coverage
+.pytest_cache/
+
+# Runtime logs
+logs/
+
+# OS metadata
+.DS_Store
+Thumbs.db
+
+# Linting
+.ruff_cache/
+
+# Type checking
+.mypy_cache/
+
+# IDE
+.vscode/
+
+# AI files
+.claude/
+CLAUDE.md
+
+# MkDocs build output
+site/
+
+# uv-forge files
+.dev
+
+

uv_forger-0.1.0/.python-version

@@ -0,0 +1 @@
+3.14

uv_forger-0.1.0/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2026-03-10
+
+### Added
+
+- Initial release of UV Forge
+- Flet desktop GUI for scaffolding Python projects with UV
+- 10 UI framework templates (Flet, PyQt6, PySide6, tkinter, customtkinter, Kivy, Pygame, NiceGUI, Streamlit, Gradio)
+- 21 project type templates (Django, FastAPI, Flask, data science, ML, CLI tools, APIs, web scraping, and more)
+- JSON-based template system with fallback hierarchy and intelligent merging
+- Smart scaffolding with boilerplate file content and `{{project_name}}` placeholder substitution
+- PyPI name availability checker with PEP 503 normalization
+- Two-phase git integration (local repo + bare hub, auto commit and push)
+- Dev dependency support (`uv add --dev`) with amber badge in UI
+- Project metadata dialog (author, email, description, SPDX license)
+- Post-build automation with configurable shell commands
+- Rollback system for cleanup on build failure
+- Named project presets with 4 built-in starters
+- Recent projects history (last 5 builds)
+- Persistent settings (project path, GitHub root, Python version, IDE, git defaults)
+- Colour-coded log viewer with clickable source locations
+- Dark and light theme toggle
+
+[0.1.0]: https://github.com/oktl/uv-forge/releases/tag/v0.1.0

uv_forger-0.1.0/CODE-OF-CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

uv_forger-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,101 @@
+# Contributing to UV Forge
+
+Thanks for your interest in contributing! UV Forge is a Flet desktop app for scaffolding Python projects with `uv`, and there are plenty of ways to help out — from reporting bugs to adding new project templates.
+
+---
+
+## Ways to Contribute
+
+- **Bug reports** — Found something broken? Open an issue with steps to reproduce, your OS, and Python version.
+- **Feature requests** — Have an idea? Open an issue and describe the use case.
+- **New templates** — The easiest contribution. Add a new UI framework or project type — no core code changes needed in most cases.
+- **New boilerplate** — Drop starter file content into `uv_forge/config/templates/boilerplate/` — also no code changes required.
+- **Bug fixes and features** — Fork, branch, fix, test, PR. See below.
+- **Docs** — Improvements to the [README](README.md), in-app Help text ([`uv_forge/assets/docs/HELP.md`](uv_forge/assets/docs/HELP.md)), or code comments are always welcome.
+
+---
+
+## Development Setup
+
+You'll need Python 3.12+, `uv`, and Git.
+
+```bash
+git clone https://github.com/oktl/uv-forge.git
+cd uv-forge
+uv run uv-forger        # Run the app
+uv run pytest          # Run the test suite (625 tests)
+uv run ruff check uv_forge  # Lint
+uv run ruff format uv_forge # Format
+```
+
+A pre-commit hook runs `ruff` automatically on commit, so you'll catch lint issues before pushing.
+
+---
+
+## Adding a New Framework or Project Type
+
+This is the most common kind of contribution and is largely declarative:
+
+1. **Add the name** to `UI_FRAMEWORKS` or `PROJECT_TYPE_PACKAGE_MAP` in `uv_forge/core/constants.py`
+2. **Add the package mapping** to `FRAMEWORK_PACKAGE_MAP` (UI frameworks only)
+3. **Add a display entry** to `UI_FRAMEWORK_CATEGORIES` or `PROJECT_TYPE_CATEGORIES` in `uv_forge/ui/dialog_data.py`
+4. **Create a template JSON** in `uv_forge/config/templates/ui_frameworks/` or `uv_forge/config/templates/project_types/`
+5. **Optionally add boilerplate** — drop starter files into `uv_forge/config/templates/boilerplate/ui_frameworks/<name>/` or `boilerplate/project_types/<name>/`. Uses `{{project_name}}` as a placeholder. No code changes needed.
+
+The template JSON format:
+
+```json
+{
+  "name": "src",
+  "create_init": true,
+  "root_level": false,
+  "subfolders": [],
+  "files": ["main.py", "config.py"]
+}
+```
+
+Look at an existing template (e.g. `uv_forge/config/templates/ui_frameworks/flet.json`) for reference.
+
+---
+
+## Code Style
+
+- **Linter/formatter:** Ruff — rules `E`, `F`, `I`, `W`, `UP`, `B`, `SIM`
+- **Imports:** Absolute `uv_forge.*` paths only (e.g. `from uv_forge.core.state import AppState`)
+- **Type hints:** Use `str | None` not `Optional[str]`; `collections.abc.Callable` not `typing.Callable`
+- **Models:** Dataclasses for new data structures
+- **Async:** Wrap coroutines with `wrap_async()` for Flet callbacks; use `AsyncExecutor.run()` for subprocess calls
+
+---
+
+## Testing
+
+Run the full suite before opening a PR:
+
+```bash
+uv run pytest
+```
+
+Tests live in `tests/`, mirroring the `uv_forge/` structure. `pytest-asyncio` is configured in auto mode — async test functions just work.
+
+**Please add tests** for any new functionality in `tests/core/`, `tests/handlers/`, or `tests/ui/`. Handler tests use `Handlers(MockPage(), MockControls(), AppState())` — no real Flet runtime needed.
+
+Coverage is generated automatically. Aim to maintain or improve existing coverage.
+
+---
+
+## Submitting a Pull Request
+
+1. Fork the repo and create a branch from `main`
+2. Make your changes
+3. Run `uv run pytest` — all tests must pass
+4. Run `uv run ruff check uv_forge` — no lint errors
+5. Open a PR with a clear description of what changed and why
+
+Small, focused PRs are much easier to review than large ones. If you're planning something significant, open an issue first so we can discuss the approach.
+
+---
+
+## Questions?
+
+Open a [GitHub issue](https://github.com/oktl/uv-forge/issues) — happy to help get you oriented.

uv_forger-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Tim Lang
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.