gitpr-cli 1.4.4__tar.gz → 1.6.0__tar.gz

{gitpr_cli-1.4.4/gitpr_cli.egg-info → gitpr_cli-1.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gitpr-cli
-Version: 1.4.4
+Version: 1.6.0
 Summary: AI-powered PR automation, commit messages, and code review (Gemini, DeepSeek, and Ollama)
 Author-email: Natan Fiuza <contato@natanfiuza.dev.br>
 Requires-Python: >=3.10
@@ -194,6 +194,7 @@ You can pass the following *flags* for specific actions:
   * **New Code Issue (`gitpr -is`):** Reads the current `git diff`. **Why use:** Ideal for quickly documenting the task you just finished programming, before committing.
   * **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.
   * **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.
+* `--close-issue` / `--no-close-issue`: Control the **automatic issue closure**. After `gitpr -is` creates an issue on GitHub, the next `gitpr` run offers to add `close #N` to the Pull Request description — the record lives in `.gitpr/conf/github.yml`, which GitPR adds to `.gitignore` automatically. `--close-issue` accepts without asking, `--no-close-issue` skips the check for the run, and `GITPR_ISSUE_AUTOCLOSE=false` turns the feature off. 📖 [Full docs](https://gitpr.natanfiuza.dev.br/docs/issue-autoclose)
 * **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, GitLab, Bitbucket, or Azure DevOps via REST API. Before generation, it checks for unstaged files, calculates suggested reviewers, 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, optional auto-merge, and clear error feedback when merge conflicts occur. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://gitpr.natanfiuza.dev.br/docs/pull-request-publication)
 * `-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.
 * `-u` or `--update`: Checks the latest version of GitPR on PyPI and shows how to update it (Auto-Updater).
@@ -339,6 +340,23 @@ For your own README there is a static badge. `gitpr badge --readme` prints the l
 
 📖 **Full documentation:** [gitpr.natanfiuza.dev.br/docs/badge](https://gitpr.natanfiuza.dev.br/docs/badge)
 
+## 🔗 Automatic Issue Closure (--close-issue)
+
+`gitpr -is` creates an issue, and the pull request is where it gets closed. This feature carries the number between the two: when `F3` creates the issue on GitHub, GitPR records it in `.gitpr/conf/github.yml` (added to `.gitignore` automatically) — one issue at a time, the last one wins.
+
+On the next `gitpr` run, before the description is generated, GitPR checks the recorded issue on GitHub. While it is still open, it offers to add `close #N` to the pull request body; the line becomes its own paragraph at the end and is never duplicated. Merging the pull request then closes the issue automatically.
+
+| Flag / setting | Effect |
+|---|---|
+| `--close-issue` | Adds the line without asking (the issue is still checked) |
+| `--no-close-issue` | Skips the check for this run — no record is read and no forge call is made |
+| `GITPR_ISSUE_AUTOCLOSE=false` | Turns the feature off for every run; `--close-issue` does not override it |
+| `GITPR_ISSUE_AUTOCLOSE_TIMEOUT` | Seconds to wait for the forge while checking the issue (default `5`) |
+
+GitHub only; the other forges skip the feature in silence. A run with no terminal does not ask — use `--close-issue` to opt in. The record survives a failed or cancelled publish and is cleared only after the body reaches the forge; a closed, deleted or pull-request number forgets itself, and a record from another repository is ignored and kept.
+
+📖 **Full documentation:** [gitpr.natanfiuza.dev.br/docs/issue-autoclose](https://gitpr.natanfiuza.dev.br/docs/issue-autoclose)
+
 ## 🧠 Multi-Model Architecture (AI-Agnostic)
 
 GitPR is not tied to a single Artificial Intelligence. During initial setup, the user can choose their default engine. We currently support:
@@ -564,6 +582,7 @@ If you want to implement GitPR as an automated quality barrier in your team, che
 * [**Remote Pull Request Review (gitpr review-pr)**](https://gitpr.natanfiuza.dev.br/docs/review-pr) — How the `gitpr review-pr` subcommand reviews a pull request that is already open on the forge, fetching its diff from the API without checking out its branch.
 * [**AI Commit Messages**](https://gitpr.natanfiuza.dev.br/docs/commit-message-ia) — How to generate messages in the Conventional Commits standard and integrate with Git Hooks.
 * [**Issue Generation and TUI Interface**](https://gitpr.natanfiuza.dev.br/docs/issue-tui-help) — How to use the terminal graphical interface (TUI) and the 3 context engines to manage structured Issues.
+* [**Automatic Issue Closure (--close-issue)**](https://gitpr.natanfiuza.dev.br/docs/issue-autoclose) — How the issue created by `gitpr -is` is recorded in `.gitpr/conf/github.yml`, the gate order that decides when the next pull request offers `close #N`, why the record survives a failed publish, and how the line is kept from being duplicated.
 * [**Code Archaeologist (Git Blame)**](https://gitpr.natanfiuza.dev.br/docs/blame-arqueologo) — How to trace the origin of business rules with `git blame` and AI.
 * [**Skills and Templates System**](https://gitpr.natanfiuza.dev.br/docs/skill-template) — How to customize AI behavior with `.gitpr.*.md` files.
 * [**Release Notes & Changelog (gitpr release)**](https://gitpr.natanfiuza.dev.br/docs/release-notes) — How the `gitpr release` subcommand generates the changelog / release notes of a repository from the delta of the previous version, links every commit, pull request and contributor, suggests the next semantic version and publishes releases on the forge.

gitpr_cli-1.4.4/PKG-INFO → gitpr_cli-1.6.0/README.md

@@ -1,23 +1,3 @@
-Metadata-Version: 2.4
-Name: gitpr-cli
-Version: 1.4.4
-Summary: AI-powered PR automation, commit messages, and code review (Gemini, DeepSeek, and Ollama)
-Author-email: Natan Fiuza <contato@natanfiuza.dev.br>
-Requires-Python: >=3.10
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: click>=8.0.0
-Requires-Dist: google-genai
-Requires-Dist: openai
-Requires-Dist: python-dotenv
-Requires-Dist: cryptography
-Requires-Dist: pyyaml
-Requires-Dist: textual
-Requires-Dist: requests
-Requires-Dist: mcp>=1.0.0
-Requires-Dist: packaging>=23.0
-Dynamic: license-file
-
 
 # **GitPR CLI 🚀**
 
@@ -194,6 +174,7 @@ You can pass the following *flags* for specific actions:
   * **New Code Issue (`gitpr -is`):** Reads the current `git diff`. **Why use:** Ideal for quickly documenting the task you just finished programming, before committing.
   * **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.
   * **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.
+* `--close-issue` / `--no-close-issue`: Control the **automatic issue closure**. After `gitpr -is` creates an issue on GitHub, the next `gitpr` run offers to add `close #N` to the Pull Request description — the record lives in `.gitpr/conf/github.yml`, which GitPR adds to `.gitignore` automatically. `--close-issue` accepts without asking, `--no-close-issue` skips the check for the run, and `GITPR_ISSUE_AUTOCLOSE=false` turns the feature off. 📖 [Full docs](https://gitpr.natanfiuza.dev.br/docs/issue-autoclose)
 * **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, GitLab, Bitbucket, or Azure DevOps via REST API. Before generation, it checks for unstaged files, calculates suggested reviewers, 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, optional auto-merge, and clear error feedback when merge conflicts occur. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://gitpr.natanfiuza.dev.br/docs/pull-request-publication)
 * `-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.
 * `-u` or `--update`: Checks the latest version of GitPR on PyPI and shows how to update it (Auto-Updater).
@@ -339,6 +320,23 @@ For your own README there is a static badge. `gitpr badge --readme` prints the l
 
 📖 **Full documentation:** [gitpr.natanfiuza.dev.br/docs/badge](https://gitpr.natanfiuza.dev.br/docs/badge)
 
+## 🔗 Automatic Issue Closure (--close-issue)
+
+`gitpr -is` creates an issue, and the pull request is where it gets closed. This feature carries the number between the two: when `F3` creates the issue on GitHub, GitPR records it in `.gitpr/conf/github.yml` (added to `.gitignore` automatically) — one issue at a time, the last one wins.
+
+On the next `gitpr` run, before the description is generated, GitPR checks the recorded issue on GitHub. While it is still open, it offers to add `close #N` to the pull request body; the line becomes its own paragraph at the end and is never duplicated. Merging the pull request then closes the issue automatically.
+
+| Flag / setting | Effect |
+|---|---|
+| `--close-issue` | Adds the line without asking (the issue is still checked) |
+| `--no-close-issue` | Skips the check for this run — no record is read and no forge call is made |
+| `GITPR_ISSUE_AUTOCLOSE=false` | Turns the feature off for every run; `--close-issue` does not override it |
+| `GITPR_ISSUE_AUTOCLOSE_TIMEOUT` | Seconds to wait for the forge while checking the issue (default `5`) |
+
+GitHub only; the other forges skip the feature in silence. A run with no terminal does not ask — use `--close-issue` to opt in. The record survives a failed or cancelled publish and is cleared only after the body reaches the forge; a closed, deleted or pull-request number forgets itself, and a record from another repository is ignored and kept.
+
+📖 **Full documentation:** [gitpr.natanfiuza.dev.br/docs/issue-autoclose](https://gitpr.natanfiuza.dev.br/docs/issue-autoclose)
+
 ## 🧠 Multi-Model Architecture (AI-Agnostic)
 
 GitPR is not tied to a single Artificial Intelligence. During initial setup, the user can choose their default engine. We currently support:
@@ -564,6 +562,7 @@ If you want to implement GitPR as an automated quality barrier in your team, che
 * [**Remote Pull Request Review (gitpr review-pr)**](https://gitpr.natanfiuza.dev.br/docs/review-pr) — How the `gitpr review-pr` subcommand reviews a pull request that is already open on the forge, fetching its diff from the API without checking out its branch.
 * [**AI Commit Messages**](https://gitpr.natanfiuza.dev.br/docs/commit-message-ia) — How to generate messages in the Conventional Commits standard and integrate with Git Hooks.
 * [**Issue Generation and TUI Interface**](https://gitpr.natanfiuza.dev.br/docs/issue-tui-help) — How to use the terminal graphical interface (TUI) and the 3 context engines to manage structured Issues.
+* [**Automatic Issue Closure (--close-issue)**](https://gitpr.natanfiuza.dev.br/docs/issue-autoclose) — How the issue created by `gitpr -is` is recorded in `.gitpr/conf/github.yml`, the gate order that decides when the next pull request offers `close #N`, why the record survives a failed publish, and how the line is kept from being duplicated.
 * [**Code Archaeologist (Git Blame)**](https://gitpr.natanfiuza.dev.br/docs/blame-arqueologo) — How to trace the origin of business rules with `git blame` and AI.
 * [**Skills and Templates System**](https://gitpr.natanfiuza.dev.br/docs/skill-template) — How to customize AI behavior with `.gitpr.*.md` files.
 * [**Release Notes & Changelog (gitpr release)**](https://gitpr.natanfiuza.dev.br/docs/release-notes) — How the `gitpr release` subcommand generates the changelog / release notes of a repository from the delta of the previous version, links every commit, pull request and contributor, suggests the next semantic version and publishes releases on the forge.

gitpr_cli-1.4.4/README.md → gitpr_cli-1.6.0/gitpr_cli.egg-info/PKG-INFO

@@ -1,3 +1,23 @@
+Metadata-Version: 2.4
+Name: gitpr-cli
+Version: 1.6.0
+Summary: AI-powered PR automation, commit messages, and code review (Gemini, DeepSeek, and Ollama)
+Author-email: Natan Fiuza <contato@natanfiuza.dev.br>
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: click>=8.0.0
+Requires-Dist: google-genai
+Requires-Dist: openai
+Requires-Dist: python-dotenv
+Requires-Dist: cryptography
+Requires-Dist: pyyaml
+Requires-Dist: textual
+Requires-Dist: requests
+Requires-Dist: mcp>=1.0.0
+Requires-Dist: packaging>=23.0
+Dynamic: license-file
+
 
 # **GitPR CLI 🚀**
 
@@ -174,6 +194,7 @@ You can pass the following *flags* for specific actions:
   * **New Code Issue (`gitpr -is`):** Reads the current `git diff`. **Why use:** Ideal for quickly documenting the task you just finished programming, before committing.
   * **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.
   * **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.
+* `--close-issue` / `--no-close-issue`: Control the **automatic issue closure**. After `gitpr -is` creates an issue on GitHub, the next `gitpr` run offers to add `close #N` to the Pull Request description — the record lives in `.gitpr/conf/github.yml`, which GitPR adds to `.gitignore` automatically. `--close-issue` accepts without asking, `--no-close-issue` skips the check for the run, and `GITPR_ISSUE_AUTOCLOSE=false` turns the feature off. 📖 [Full docs](https://gitpr.natanfiuza.dev.br/docs/issue-autoclose)
 * **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, GitLab, Bitbucket, or Azure DevOps via REST API. Before generation, it checks for unstaged files, calculates suggested reviewers, 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, optional auto-merge, and clear error feedback when merge conflicts occur. Use `--base <branch>` to change the target branch. 📖 [Full docs](https://gitpr.natanfiuza.dev.br/docs/pull-request-publication)
 * `-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.
 * `-u` or `--update`: Checks the latest version of GitPR on PyPI and shows how to update it (Auto-Updater).
@@ -319,6 +340,23 @@ For your own README there is a static badge. `gitpr badge --readme` prints the l
 
 📖 **Full documentation:** [gitpr.natanfiuza.dev.br/docs/badge](https://gitpr.natanfiuza.dev.br/docs/badge)
 
+## 🔗 Automatic Issue Closure (--close-issue)
+
+`gitpr -is` creates an issue, and the pull request is where it gets closed. This feature carries the number between the two: when `F3` creates the issue on GitHub, GitPR records it in `.gitpr/conf/github.yml` (added to `.gitignore` automatically) — one issue at a time, the last one wins.
+
+On the next `gitpr` run, before the description is generated, GitPR checks the recorded issue on GitHub. While it is still open, it offers to add `close #N` to the pull request body; the line becomes its own paragraph at the end and is never duplicated. Merging the pull request then closes the issue automatically.
+
+| Flag / setting | Effect |
+|---|---|
+| `--close-issue` | Adds the line without asking (the issue is still checked) |
+| `--no-close-issue` | Skips the check for this run — no record is read and no forge call is made |
+| `GITPR_ISSUE_AUTOCLOSE=false` | Turns the feature off for every run; `--close-issue` does not override it |
+| `GITPR_ISSUE_AUTOCLOSE_TIMEOUT` | Seconds to wait for the forge while checking the issue (default `5`) |
+
+GitHub only; the other forges skip the feature in silence. A run with no terminal does not ask — use `--close-issue` to opt in. The record survives a failed or cancelled publish and is cleared only after the body reaches the forge; a closed, deleted or pull-request number forgets itself, and a record from another repository is ignored and kept.
+
+📖 **Full documentation:** [gitpr.natanfiuza.dev.br/docs/issue-autoclose](https://gitpr.natanfiuza.dev.br/docs/issue-autoclose)
+
 ## 🧠 Multi-Model Architecture (AI-Agnostic)
 
 GitPR is not tied to a single Artificial Intelligence. During initial setup, the user can choose their default engine. We currently support:
@@ -544,6 +582,7 @@ If you want to implement GitPR as an automated quality barrier in your team, che
 * [**Remote Pull Request Review (gitpr review-pr)**](https://gitpr.natanfiuza.dev.br/docs/review-pr) — How the `gitpr review-pr` subcommand reviews a pull request that is already open on the forge, fetching its diff from the API without checking out its branch.
 * [**AI Commit Messages**](https://gitpr.natanfiuza.dev.br/docs/commit-message-ia) — How to generate messages in the Conventional Commits standard and integrate with Git Hooks.
 * [**Issue Generation and TUI Interface**](https://gitpr.natanfiuza.dev.br/docs/issue-tui-help) — How to use the terminal graphical interface (TUI) and the 3 context engines to manage structured Issues.
+* [**Automatic Issue Closure (--close-issue)**](https://gitpr.natanfiuza.dev.br/docs/issue-autoclose) — How the issue created by `gitpr -is` is recorded in `.gitpr/conf/github.yml`, the gate order that decides when the next pull request offers `close #N`, why the record survives a failed publish, and how the line is kept from being duplicated.
 * [**Code Archaeologist (Git Blame)**](https://gitpr.natanfiuza.dev.br/docs/blame-arqueologo) — How to trace the origin of business rules with `git blame` and AI.
 * [**Skills and Templates System**](https://gitpr.natanfiuza.dev.br/docs/skill-template) — How to customize AI behavior with `.gitpr.*.md` files.
 * [**Release Notes & Changelog (gitpr release)**](https://gitpr.natanfiuza.dev.br/docs/release-notes) — How the `gitpr release` subcommand generates the changelog / release notes of a repository from the delta of the previous version, links every commit, pull request and contributor, suggests the next semantic version and publishes releases on the forge.

{gitpr_cli-1.4.4 → gitpr_cli-1.6.0}/gitpr_cli.egg-info/SOURCES.txt

@@ -29,11 +29,14 @@ src/main.py
 src/mcp_server.py
 src/metrics.py
 src/net.py
+src/project_config.py
 src/release_engine.py
 src/reviewer_resolution.py
 src/reviewer_suggestion.py
+src/scm_settings.py
 src/security.py
 src/security_ruleset.py
+src/skill_frontmatter.py
 src/spinner.py
 src/suggest_reviewers.py
 src/tui_issue.py
@@ -136,6 +139,11 @@ src/infrastructure/scm/factory.py
 src/infrastructure/scm/github_provider.py
 src/infrastructure/scm/gitlab_provider.py
 src/infrastructure/scm/web_links.py
+src/issue_autoclose/__init__.py
+src/issue_autoclose/insert_close_line.py
+src/issue_autoclose/issue_registry.py
+src/issue_autoclose/register_created_issue.py
+src/issue_autoclose/resolve_close_issue.py
 src/policy_packs/laravel-quality/CHANGELOG.md
 src/policy_packs/laravel-quality/README.md
 src/policy_packs/laravel-quality/linter.yml
@@ -169,6 +177,7 @@ src/ui/issue_app.py
 src/ui/linter_app.py
 src/ui/metrics_app.py
 src/ui/metrics_migration_app.py
+src/ui/pr_base_app.py
 src/ui/pr_publish_app.py
 src/ui/pr_publish_help.py
 src/ui/demo/__init__.py
@@ -181,10 +190,12 @@ tests/test_blame_metrics.py
 tests/test_changelog_builder.py
 tests/test_chat_backend.py
 tests/test_check_cli.py
+tests/test_cli_help.py
 tests/test_commit_app.py
 tests/test_commit_classifier.py
 tests/test_config_app.py
 tests/test_config_cli.py
+tests/test_config_issue_autoclose.py
 tests/test_config_schema.py
 tests/test_config_store.py
 tests/test_config_suggest_reviewers.py
@@ -192,6 +203,7 @@ tests/test_config_validation.py
 tests/test_core.py
 tests/test_diff_failure_cli.py
 tests/test_diff_parser.py
+tests/test_doc_links.py
 tests/test_explain_command.py
 tests/test_external_linters.py
 tests/test_full_diff_encoding.py
@@ -209,22 +221,28 @@ tests/test_metrics.py
 tests/test_net_timeouts.py
 tests/test_plugins.py
 tests/test_policy_cli.py
+tests/test_pr_base_app.py
 tests/test_pr_publish_app.py
 tests/test_pr_publish_linter_modal.py
 tests/test_pre_save.py
+tests/test_project_config.py
+tests/test_project_config_cli.py
 tests/test_release_cli.py
 tests/test_release_engine.py
 tests/test_reviewer_resolution.py
 tests/test_reviewer_suggestion.py
 tests/test_risk_cli.py
 tests/test_security_ruleset.py
+tests/test_seed_command.py
 tests/test_skill_command.py
 tests/test_skill_context.py
+tests/test_skill_frontmatter.py
 tests/test_skill_templates.py
 tests/test_smart_excludes.py
 tests/test_suggest_reviewers.py
 tests/test_tests_command.py
 tests/test_thinking_words.py
+tests/test_tui_issue_token.py
 tests/test_updater.py
 tests/test_usage_log.py
 tests/test_version_bump.py

{gitpr_cli-1.4.4 → gitpr_cli-1.6.0}/pyproject.toml

@@ -1,49 +1,49 @@
-[build-system]
-requires = ["setuptools>=61.0"]
-build-backend = "setuptools.build_meta"
-
-[project]
-name = "gitpr-cli"
-dynamic = ["version"]
-description = "AI-powered PR automation, commit messages, and code review (Gemini, DeepSeek, and Ollama)"
-readme = "README.md"
-requires-python = ">=3.10"
-authors = [
-    {name = "Natan Fiuza", email = "contato@natanfiuza.dev.br"}
-]
-dependencies = [
-    "click>=8.0.0",
-    "google-genai",
-    "openai",
-    "python-dotenv",
-    "cryptography",
-    "pyyaml",
-    "textual",
-    "requests",
-    "mcp>=1.0.0",
-    "packaging>=23.0"
-]
-
-[project.scripts]
-gitpr = "src.main:cli"
-gitpr-mcp = "src.mcp_server:main"
-
-[tool.setuptools.packages.find]
-where = ["."]
-include = ["src", "src.*"]
-
-# The bundled policy packs are data, not code: the four directories under
-# src/policy_packs ship inside the wheel, and without this block a built package
-# would find no packs at all while the source tree found four. MANIFEST.in is
-# not used anywhere in this project, so there is one place to look.
-[tool.setuptools.package-data]
-"src.policy_packs" = ["**/*.yml", "**/*.yaml", "**/*.md"]
-
-[tool.setuptools.dynamic]
-version = {attr = "src.updater.__version__"}
-
-[tool.pyright]
-include = ["src"]
-executionEnvironments = [
-  { root = "." }
+[build-system]
+requires = ["setuptools>=61.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "gitpr-cli"
+dynamic = ["version"]
+description = "AI-powered PR automation, commit messages, and code review (Gemini, DeepSeek, and Ollama)"
+readme = "README.md"
+requires-python = ">=3.10"
+authors = [
+    {name = "Natan Fiuza", email = "contato@natanfiuza.dev.br"}
+]
+dependencies = [
+    "click>=8.0.0",
+    "google-genai",
+    "openai",
+    "python-dotenv",
+    "cryptography",
+    "pyyaml",
+    "textual",
+    "requests",
+    "mcp>=1.0.0",
+    "packaging>=23.0"
+]
+
+[project.scripts]
+gitpr = "src.main:cli"
+gitpr-mcp = "src.mcp_server:main"
+
+[tool.setuptools.packages.find]
+where = ["."]
+include = ["src", "src.*"]
+
+# The bundled policy packs are data, not code: the four directories under
+# src/policy_packs ship inside the wheel, and without this block a built package
+# would find no packs at all while the source tree found four. MANIFEST.in is
+# not used anywhere in this project, so there is one place to look.
+[tool.setuptools.package-data]
+"src.policy_packs" = ["**/*.yml", "**/*.yaml", "**/*.md"]
+
+[tool.setuptools.dynamic]
+version = {attr = "src.updater.__version__"}
+
+[tool.pyright]
+include = ["src"]
+executionEnvironments = [
+  { root = "." }
 ]

{gitpr_cli-1.4.4 → gitpr_cli-1.6.0}/src/__init__.py

@@ -1 +1 @@
-# Módulo principal do GitPR
+# Módulo principal do GitPR

{gitpr_cli-1.4.4 → gitpr_cli-1.6.0}/src/application/__init__.py

@@ -1,2 +1,2 @@
-# Application layer markers
-
+# Application layer markers
+

{gitpr_cli-1.4.4 → gitpr_cli-1.6.0}/src/application/use_cases/__init__.py

@@ -1,8 +1,8 @@
-from src.application.use_cases.generate_test_file import generate_test_file, validate_test_syntax
-from src.application.use_cases.generate_pr_explanation import generate_pr_explanation
-
-__all__ = [
-    "generate_test_file",
-    "validate_test_syntax",
-    "generate_pr_explanation",
-]
+from src.application.use_cases.generate_test_file import generate_test_file, validate_test_syntax
+from src.application.use_cases.generate_pr_explanation import generate_pr_explanation
+
+__all__ = [
+    "generate_test_file",
+    "validate_test_syntax",
+    "generate_pr_explanation",
+]

{gitpr_cli-1.4.4 → gitpr_cli-1.6.0}/src/application/use_cases/activate_policy_pack.py

@@ -1,122 +1,122 @@
-"""Use case: record which pack a repository follows.
-
-The record is ``.gitpr/policy.lock.yml``, a file meant to be committed: it is
-what makes the policy the same for everyone on the team and what lets a later
-run notice that a pack changed under it.
-
-Activation is **one pack per repository**. Choosing a second one replaces the
-first rather than adding to it, so there is never a question about which pack
-owns a value — the graph below the root is reached through ``extends``, and only
-through it.
-
-Building the lockfile and writing it are separate functions because the CLI has
-to show the user what will be written *before* asking whether to write it. A
-command that writes first and asks afterwards is not asking.
-"""
-
-import os
-from datetime import datetime, timezone
-from typing import Any
-
-from src.domain.policy import set_active_policy
-from src.domain.policy.policy_resolver import resolve_graph
-from src.i18n import __
-from src.infrastructure.policy.local_policy_repository import (
-    LOCKFILE_SCHEMA_VERSION,
-    lockfile_path,
-    write_lockfile,
-)
-from src.infrastructure.policy.policy_pack_loader import (
-    load_pack_by_reference,
-    make_loader,
-)
-
-from src.application.use_cases.validate_policy_pack import split_reference
-
-
-def _relative_to_repo(absolute: str, repo_path: str) -> str | None:
-    """*absolute* as a repository-relative POSIX path, or None when outside.
-
-    Only packs that live inside the repository are recorded by path. A pack in
-    ``~/.gitpr/policies/`` is recorded by name and version instead, so the
-    lockfile stays valid for a teammate who has it installed somewhere else.
-    """
-    try:
-        relative = os.path.relpath(absolute, repo_path)
-    except ValueError:
-        # Different drives on Windows.
-        return None
-    parts = relative.split(os.sep)
-    if not relative or parts[0] == "..":
-        return None
-    return relative.replace(os.sep, "/")
-
-
-def _lockfile_entry(pack: Any, repo_path: str) -> dict[str, Any]:
-    entry: dict[str, Any] = {
-        "name": pack.reference.name,
-        "version": pack.reference.version,
-        "source": pack.reference.source.value,
-        "checksum": pack.reference.checksum,
-    }
-    if pack.reference.path:
-        relative = _relative_to_repo(pack.reference.path, repo_path)
-        if relative:
-            entry["path"] = relative
-    return entry
-
-
-def build_lockfile(root_reference: str, repo_path: str | None = None) -> dict[str, Any]:
-    """Resolves *root_reference* and the lockfile that would pin it.
-
-    Raises ``PolicyError`` when the pack cannot be found or its graph does not
-    resolve, and writes nothing. The CLI calls this first, shows the result, and
-    only then decides whether to call :func:`activate_policy_pack`.
-    """
-    from src.updater import __version__
-
-    repo = os.path.abspath(repo_path or os.getcwd())
-    name, version_range = split_reference(root_reference)
-    root = load_pack_by_reference(name, version_range, repo)
-    packs = resolve_graph(root, make_loader(repo))
-
-    return {
-        "schema_version": LOCKFILE_SCHEMA_VERSION,
-        "gitpr_version": __version__,
-        "activated_at": datetime.now(timezone.utc).isoformat(timespec="seconds"),
-        "root": _lockfile_entry(root, repo),
-        "packs": [_lockfile_entry(pack, repo) for pack in packs],
-    }
-
-
-def activate_policy_pack(root_reference: str, repo_path: str | None = None) -> str:
-    """Pins *root_reference* for the repository and returns the lockfile path."""
-    data = build_lockfile(root_reference, repo_path)
-    return write_lockfile(data, repo_path)
-
-
-def deactivate_policy_pack(repo_path: str | None = None) -> bool:
-    """Removes the lockfile. Returns whether there was one to remove.
-
-    The overrides file and the packs themselves are left alone: they are the
-    user's material, and a decision to stop following a pack is not a decision to
-    delete it.
-    """
-    target = lockfile_path(repo_path)
-    if not os.path.isfile(target):
-        return False
-    os.remove(target)
-    set_active_policy(None)
-    return True
-
-
-def describe_lockfile(data: dict[str, Any]) -> str:
-    """A one-line summary for the confirmation prompt."""
-    root = data.get("root") or {}
-    dependencies = [p for p in data.get("packs", []) if p.get("name") != root.get("name")]
-    return __(
-        "{pack}@{version} with {count} dependency pack(s)",
-        pack=root.get("name", "?"),
-        version=root.get("version", "?"),
-        count=len(dependencies),
-    )
+"""Use case: record which pack a repository follows.
+
+The record is ``.gitpr/policy.lock.yml``, a file meant to be committed: it is
+what makes the policy the same for everyone on the team and what lets a later
+run notice that a pack changed under it.
+
+Activation is **one pack per repository**. Choosing a second one replaces the
+first rather than adding to it, so there is never a question about which pack
+owns a value — the graph below the root is reached through ``extends``, and only
+through it.
+
+Building the lockfile and writing it are separate functions because the CLI has
+to show the user what will be written *before* asking whether to write it. A
+command that writes first and asks afterwards is not asking.
+"""
+
+import os
+from datetime import datetime, timezone
+from typing import Any
+
+from src.domain.policy import set_active_policy
+from src.domain.policy.policy_resolver import resolve_graph
+from src.i18n import __
+from src.infrastructure.policy.local_policy_repository import (
+    LOCKFILE_SCHEMA_VERSION,
+    lockfile_path,
+    write_lockfile,
+)
+from src.infrastructure.policy.policy_pack_loader import (
+    load_pack_by_reference,
+    make_loader,
+)
+
+from src.application.use_cases.validate_policy_pack import split_reference
+
+
+def _relative_to_repo(absolute: str, repo_path: str) -> str | None:
+    """*absolute* as a repository-relative POSIX path, or None when outside.
+
+    Only packs that live inside the repository are recorded by path. A pack in
+    ``~/.gitpr/policies/`` is recorded by name and version instead, so the
+    lockfile stays valid for a teammate who has it installed somewhere else.
+    """
+    try:
+        relative = os.path.relpath(absolute, repo_path)
+    except ValueError:
+        # Different drives on Windows.
+        return None
+    parts = relative.split(os.sep)
+    if not relative or parts[0] == "..":
+        return None
+    return relative.replace(os.sep, "/")
+
+
+def _lockfile_entry(pack: Any, repo_path: str) -> dict[str, Any]:
+    entry: dict[str, Any] = {
+        "name": pack.reference.name,
+        "version": pack.reference.version,
+        "source": pack.reference.source.value,
+        "checksum": pack.reference.checksum,
+    }
+    if pack.reference.path:
+        relative = _relative_to_repo(pack.reference.path, repo_path)
+        if relative:
+            entry["path"] = relative
+    return entry
+
+
+def build_lockfile(root_reference: str, repo_path: str | None = None) -> dict[str, Any]:
+    """Resolves *root_reference* and the lockfile that would pin it.
+
+    Raises ``PolicyError`` when the pack cannot be found or its graph does not
+    resolve, and writes nothing. The CLI calls this first, shows the result, and
+    only then decides whether to call :func:`activate_policy_pack`.
+    """
+    from src.updater import __version__
+
+    repo = os.path.abspath(repo_path or os.getcwd())
+    name, version_range = split_reference(root_reference)
+    root = load_pack_by_reference(name, version_range, repo)
+    packs = resolve_graph(root, make_loader(repo))
+
+    return {
+        "schema_version": LOCKFILE_SCHEMA_VERSION,
+        "gitpr_version": __version__,
+        "activated_at": datetime.now(timezone.utc).isoformat(timespec="seconds"),
+        "root": _lockfile_entry(root, repo),
+        "packs": [_lockfile_entry(pack, repo) for pack in packs],
+    }
+
+
+def activate_policy_pack(root_reference: str, repo_path: str | None = None) -> str:
+    """Pins *root_reference* for the repository and returns the lockfile path."""
+    data = build_lockfile(root_reference, repo_path)
+    return write_lockfile(data, repo_path)
+
+
+def deactivate_policy_pack(repo_path: str | None = None) -> bool:
+    """Removes the lockfile. Returns whether there was one to remove.
+
+    The overrides file and the packs themselves are left alone: they are the
+    user's material, and a decision to stop following a pack is not a decision to
+    delete it.
+    """
+    target = lockfile_path(repo_path)
+    if not os.path.isfile(target):
+        return False
+    os.remove(target)
+    set_active_policy(None)
+    return True
+
+
+def describe_lockfile(data: dict[str, Any]) -> str:
+    """A one-line summary for the confirmation prompt."""
+    root = data.get("root") or {}
+    dependencies = [p for p in data.get("packs", []) if p.get("name") != root.get("name")]
+    return __(
+        "{pack}@{version} with {count} dependency pack(s)",
+        pack=root.get("name", "?"),
+        version=root.get("version", "?"),
+        count=len(dependencies),
+    )