gitpr-cli 0.0.32__tar.gz → 0.0.33__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {gitpr_cli-0.0.32/gitpr_cli.egg-info → gitpr_cli-0.0.33}/PKG-INFO +18 -1
- gitpr_cli-0.0.32/PKG-INFO → gitpr_cli-0.0.33/README.md +419 -421
- gitpr_cli-0.0.32/README.md → gitpr_cli-0.0.33/gitpr_cli.egg-info/PKG-INFO +438 -402
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/gitpr_cli.egg-info/SOURCES.txt +3 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/blame_engine.py +6 -3
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/config.py +9 -1
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/core.py +109 -1
- gitpr_cli-0.0.33/src/github_api.py +126 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/issue_engine.py +66 -6
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/main.py +275 -16
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/ui/issue_app.py +6 -4
- gitpr_cli-0.0.33/src/ui/pr_publish_app.py +1210 -0
- gitpr_cli-0.0.33/src/ui/pr_publish_help.py +45 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/updater.py +2 -2
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/LICENSE +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/gitpr_cli.egg-info/dependency_links.txt +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/gitpr_cli.egg-info/entry_points.txt +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/gitpr_cli.egg-info/requires.txt +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/gitpr_cli.egg-info/top_level.txt +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/pyproject.toml +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/setup.cfg +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/__init__.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/ai_providers.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/cache.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/chat_memory.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/i18n.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/linter_engine.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/mcp_server.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/metrics.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/security.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/spinner.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/tui_issue.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/ui/__init__.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/ui/chat_app.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/ui/help_screen.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/src/ui/metrics_app.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_blame_metrics.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_chat_backend.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_core.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_install_wizard.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_linter_metrics.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_mcp_prompts.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_mcp_server.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_metrics.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_pre_save.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_skill_command.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_smart_excludes.py +0 -0
- {gitpr_cli-0.0.32 → gitpr_cli-0.0.33}/tests/test_thinking_words.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: gitpr-cli
|
|
3
|
-
Version: 0.0.
|
|
3
|
+
Version: 0.0.33
|
|
4
4
|
Summary: AI-powered PR automation, commit messages, and code review (Gemini, DeepSeek, and Ollama)
|
|
5
5
|
Author-email: Natan Fiuza <contato@natanfiuza.dev.br>
|
|
6
6
|
Requires-Python: >=3.10
|
|
@@ -170,6 +170,7 @@ You can pass the following *flags* for specific actions:
|
|
|
170
170
|
* **New Code Issue (`gitpr -is`):** Reads the current `git diff`. **Why use:** Ideal for quickly documenting the task you just finished programming, before committing.
|
|
171
171
|
* **Epic/Release Issue (`gitpr -is -ht`):** Reads the full history of the current branch (Git Log + PR Cache). **Why use:** Ideal for generating consolidated documentation of an entire release or a large *feature* that took several days/commits to complete.
|
|
172
172
|
* **Archaeological/Technical Debt Issue (`gitpr -is -b file:lines`):** Reads the timeline of a specific business rule. **Why use:** Ideal for documenting technical debt, explaining how a legacy code block evolved and why it needs to be refactored.
|
|
173
|
+
* **PR Publisher (default):** Running `gitpr` generates the PR description with AI, saves the `.md` file to `.gitpr/reports/pr_desc/`, and opens an interactive terminal interface (TUI) to review, edit, and publish the Pull Request directly to GitHub via REST API. Before generation, it checks for unstaged files and offers a modal to manage them. Use `--no-publish` to save only the PR file locally without opening the publisher, or `--no-edit` to auto-commit pending changes (with lint validation), auto-push, and publish immediately — handling existing PR updates and optional auto-merge. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://github.com/natanfiuza/gitpr/blob/main/docs/pull-request-publication.md)
|
|
173
174
|
* `-h` or `--help`: Shows the general help with all options. Use together with another flag for **contextual help** (e.g.: `gitpr -h --issue`, `gitpr -h --linter`) with a direct link to the detailed documentation of each feature.
|
|
174
175
|
* `-u` or `--update`: Checks and installs the latest version of GitPR (Auto-Updater).
|
|
175
176
|
|
|
@@ -341,6 +342,21 @@ GitPR automatically removes non-code files from your `git diff` before sending t
|
|
|
341
342
|
|
|
342
343
|
> 📖 **Full documentation:** [docs/smart-excludes.md](https://github.com/natanfiuza/gitpr/blob/main/docs/smart-excludes.md) — available in 5 languages (EN, PT-BR, PT-PT, FR, ES).
|
|
343
344
|
|
|
345
|
+
## 📁 Output Directory Structure
|
|
346
|
+
|
|
347
|
+
By default, GitPR saves all generated files in the `.gitpr/reports/` directory, organized by artifact type:
|
|
348
|
+
|
|
349
|
+
| Artifact | Default Location |
|
|
350
|
+
|---|---|
|
|
351
|
+
| PR Description | `.gitpr/reports/pr_desc/` |
|
|
352
|
+
| Code Review | `.gitpr/reports/review/` |
|
|
353
|
+
| Full Review | `.gitpr/reports/full_review/` |
|
|
354
|
+
| File Review | `.gitpr/reports/file_review/` |
|
|
355
|
+
| Blame Report | `.gitpr/reports/blame/` |
|
|
356
|
+
| Issue Draft | `.gitpr/reports/issue/` |
|
|
357
|
+
|
|
358
|
+
Directories are created automatically on first use. **Backward compatible:** if your `.env` already contains custom paths with directory separators (e.g., `OUTPUT_FILE_NAME=/home/user/prs/my_pr.md`), those are honored as-is — GitPR only redirects bare filenames to `.gitpr/reports/`.
|
|
359
|
+
|
|
344
360
|
## 📚 Technical Documentation and Advanced Guides
|
|
345
361
|
|
|
346
362
|
To keep this README concise, we detail the most advanced **DevOps** and **Continuous Integration** focused implementations in separate documents.
|
|
@@ -363,6 +379,7 @@ If you want to implement GitPR as an automated quality barrier in your team, che
|
|
|
363
379
|
### Core Features
|
|
364
380
|
|
|
365
381
|
* [**Pull Request (Default Mode)**](https://github.com/natanfiuza/gitpr/blob/main/docs/pr-descricao-padrao.md) — Complete flow for generating PR descriptions without flags.
|
|
382
|
+
* [**Pull Request Publisher TUI**](https://github.com/natanfiuza/gitpr/blob/main/docs/pull-request-publication.md) — How to review and publish Pull Requests directly to GitHub from the terminal.
|
|
366
383
|
* [**AI Code Review**](https://github.com/natanfiuza/gitpr/blob/main/docs/code-review-ia.md) — Guide to review modes (`--review`, `--fullreview`) and file auditing (`--input`).
|
|
367
384
|
* [**AI Commit Messages**](https://github.com/natanfiuza/gitpr/blob/main/docs/commit-message-ia.md) — How to generate messages in the Conventional Commits standard and integrate with Git Hooks.
|
|
368
385
|
* [**Issue Generation and TUI Interface**](https://github.com/natanfiuza/gitpr/blob/main/docs/issue-tui-help.md) — How to use the terminal graphical interface (TUI) and the 3 context engines to manage structured Issues.
|