ai-cr 3.2.1__py3-none-any.whl → 3.3.0__py3-none-any.whl

gito/tpl/github_workflows/components/env-vars.j2

@@ -1,11 +1,11 @@
-
-        LLM_API_TYPE: {{ api_type }}
-        LLM_API_KEY: {{ "${{ secrets." + secret_name + " }}" }}
-        MODEL: {{ model }}
-        {% raw -%}
-        JIRA_TOKEN: ${{ secrets.JIRA_TOKEN }}
-        JIRA_URL: ${{ secrets.JIRA_URL }}
-        JIRA_USER: ${{ secrets.JIRA_USER }}
-        LINEAR_API_KEY: ${{ secrets.LINEAR_API_KEY }}
-        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        {%- endraw %}
+
+        LLM_API_TYPE: {{ api_type }}
+        LLM_API_KEY: {{ "${{ secrets." + secret_name + " }}" }}
+        MODEL: {{ model }}
+        {% raw -%}
+        JIRA_TOKEN: ${{ secrets.JIRA_TOKEN }}
+        JIRA_URL: ${{ secrets.JIRA_URL }}
+        JIRA_USER: ${{ secrets.JIRA_USER }}
+        LINEAR_API_KEY: ${{ secrets.LINEAR_API_KEY }}
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        {%- endraw %}

gito/tpl/github_workflows/components/installs.j2

@@ -1,23 +1,23 @@
-
-
-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with: { python-version: "3.13" }
-
-    - name: Fetch Latest Gito Version
-      id: gito-version
-      run: pip index versions gito.bot 2>/dev/null | head -1 | sed -n 's/.* (\([^)]*\)).*/version=\1/p' >> $GITHUB_OUTPUT
-
-    {% raw -%}
-    - uses: actions/cache@v4
-      id: cache
-      with:
-        path: |
-          ${{ env.pythonLocation }}/lib/python3.13/site-packages
-          ${{ env.pythonLocation }}/bin
-        key: gito_v${{ steps.gito-version.outputs.version }}
-    {%- endraw %}
-
-    - name: Install Gito
-      if: steps.cache.outputs.cache-hit != 'true'
-      run: pip install gito.bot~={{ major }}.{{ minor }}
+
+
+    - name: Set up Python
+      uses: actions/setup-python@v5
+      with: { python-version: "3.13" }
+
+    - name: Fetch Latest Gito Version
+      id: gito-version
+      run: pip index versions gito.bot 2>/dev/null | head -1 | sed -n 's/.* (\([^)]*\)).*/version=\1/p' >> $GITHUB_OUTPUT
+
+    {% raw -%}
+    - uses: actions/cache@v4
+      id: cache
+      with:
+        path: |
+          ${{ env.pythonLocation }}/lib/python3.13/site-packages
+          ${{ env.pythonLocation }}/bin
+        key: gito_v${{ steps.gito-version.outputs.version }}
+    {%- endraw %}
+
+    - name: Install Gito
+      if: steps.cache.outputs.cache-hit != 'true'
+      run: pip install gito.bot~={{ major }}.{{ minor }}

gito/tpl/github_workflows/gito-code-review.yml.j2

@@ -1,33 +1,33 @@
-name: "Gito: AI Code Reviewer"
-on:
-  pull_request:
-    types: [opened, synchronize, reopened]
-  workflow_dispatch:
-    inputs:
-      pr_number:
-        description: "Pull Request number"
-        required: true
-jobs:
-  review:
-    runs-on: ubuntu-latest
-    permissions: { contents: read, pull-requests: write } # 'write' for leaving the summary comment
-    steps:
-    - uses: actions/checkout@v4
-      with: { fetch-depth: 0 }
-
-    {%- include("github_workflows/components/installs.j2") %}
-
-    - name: Run AI code review
-      env:
-        {%- include("github_workflows/components/env-vars.j2") %}
-        PR_NUMBER_FROM_WORKFLOW_DISPATCH: {% raw %}${{ github.event.inputs.pr_number }}{% endraw %}
-      run: |{% raw %}
-        gito --verbose review
-        gito github-comment{% endraw %}
-
-    - uses: actions/upload-artifact@v4
-      with:
-        name: gito-code-review-results
-        path: |
-          code-review-report.md
+name: "Gito: AI Code Reviewer"
+on:
+  pull_request:
+    types: [opened, synchronize, reopened]
+  workflow_dispatch:
+    inputs:
+      pr_number:
+        description: "Pull Request number"
+        required: true
+jobs:
+  review:
+    runs-on: ubuntu-latest
+    permissions: { contents: read, pull-requests: write } # 'write' for leaving the summary comment
+    steps:
+    - uses: actions/checkout@v4
+      with: { fetch-depth: 0 }
+
+    {%- include("github_workflows/components/installs.j2") %}
+
+    - name: Run AI code review
+      env:
+        {%- include("github_workflows/components/env-vars.j2") %}
+        PR_NUMBER_FROM_WORKFLOW_DISPATCH: {% raw %}${{ github.event.inputs.pr_number }}{% endraw %}
+      run: |{% raw %}
+        gito --verbose review
+        gito github-comment{% endraw %}
+
+    - uses: actions/upload-artifact@v4
+      with:
+        name: gito-code-review-results
+        path: |
+          code-review-report.md
           code-review-report.json

gito/tpl/github_workflows/gito-react-to-comments.yml.j2

@@ -1,70 +1,70 @@
-name: "Gito: React to GitHub comment"
-
-on:
-  issue_comment:
-    types: [created]
-
-permissions:
-  contents: write  # to make PR
-  issues: write
-  pull-requests: write
-  # read: to download the code review artifact
-  # write: to trigger other actions
-  actions: write
-
-jobs:
-  process-comment:
-    if: |
-      github.event.issue.pull_request &&
-      (
-        github.event.comment.author_association == 'OWNER' ||
-        github.event.comment.author_association == 'MEMBER' ||
-        github.event.comment.author_association == 'COLLABORATOR'
-      ) &&
-      (
-        startsWith(github.event.comment.body, '/') ||
-        startsWith(github.event.comment.body, 'gito') ||
-        startsWith(github.event.comment.body, 'ai') ||
-        startsWith(github.event.comment.body, 'bot') ||
-        contains(github.event.comment.body, '@gito') ||
-        contains(github.event.comment.body, '@ai') ||
-        contains(github.event.comment.body, '@bot')
-      )
-    runs-on: ubuntu-latest
-
-    steps:
-    - name: Get PR details
-      id: pr
-      uses: actions/github-script@v7
-      with:
-        script: |
-          const pr = await github.rest.pulls.get({
-            owner: context.repo.owner,
-            repo: context.repo.repo,
-            pull_number: context.issue.number
-          });
-          return {
-            head_ref: pr.data.head.ref,
-            head_sha: pr.data.head.sha,
-            base_ref: pr.data.base.ref
-          };
-
-    - name: Checkout repository
-      uses: actions/checkout@v4
-      with:
-        {% raw -%}
-        repository: ${{ github.repository }}
-        token: ${{ secrets.GITHUB_TOKEN }}
-        ref: ${{ fromJson(steps.pr.outputs.result).head_ref }}
-        fetch-depth: 0
-        {%- endraw %}
-
-      {%- include("github_workflows/components/installs.j2") %}
-
-    - name: Run Gito react
-      env:
-        # LLM config is needed only if answer_github_comments = true in .gito/config.toml
-        # Otherwise, use LLM_API_TYPE: none
-        {%- include("github_workflows/components/env-vars.j2") %}
-      run: |
-        {% raw %}gito react-to-comment ${{ github.event.comment.id }}{%- endraw %}
+name: "Gito: React to GitHub comment"
+
+on:
+  issue_comment:
+    types: [created]
+
+permissions:
+  contents: write  # to make PR
+  issues: write
+  pull-requests: write
+  # read: to download the code review artifact
+  # write: to trigger other actions
+  actions: write
+
+jobs:
+  process-comment:
+    if: |
+      github.event.issue.pull_request &&
+      (
+        github.event.comment.author_association == 'OWNER' ||
+        github.event.comment.author_association == 'MEMBER' ||
+        github.event.comment.author_association == 'COLLABORATOR'
+      ) &&
+      (
+        startsWith(github.event.comment.body, '/') ||
+        startsWith(github.event.comment.body, 'gito') ||
+        startsWith(github.event.comment.body, 'ai') ||
+        startsWith(github.event.comment.body, 'bot') ||
+        contains(github.event.comment.body, '@gito') ||
+        contains(github.event.comment.body, '@ai') ||
+        contains(github.event.comment.body, '@bot')
+      )
+    runs-on: ubuntu-latest
+
+    steps:
+    - name: Get PR details
+      id: pr
+      uses: actions/github-script@v7
+      with:
+        script: |
+          const pr = await github.rest.pulls.get({
+            owner: context.repo.owner,
+            repo: context.repo.repo,
+            pull_number: context.issue.number
+          });
+          return {
+            head_ref: pr.data.head.ref,
+            head_sha: pr.data.head.sha,
+            base_ref: pr.data.base.ref
+          };
+
+    - name: Checkout repository
+      uses: actions/checkout@v4
+      with:
+        {% raw -%}
+        repository: ${{ github.repository }}
+        token: ${{ secrets.GITHUB_TOKEN }}
+        ref: ${{ fromJson(steps.pr.outputs.result).head_ref }}
+        fetch-depth: 0
+        {%- endraw %}
+
+      {%- include("github_workflows/components/installs.j2") %}
+
+    - name: Run Gito react
+      env:
+        # LLM config is needed only if answer_github_comments = true in .gito/config.toml
+        # Otherwise, use LLM_API_TYPE: none
+        {%- include("github_workflows/components/env-vars.j2") %}
+      run: |
+        {% raw %}gito react-to-comment ${{ github.event.comment.id }}{%- endraw %}

gito/tpl/partial/aux_files.j2

@@ -1,8 +1,8 @@
-{% if aux_files %}
-----AUXILIARY INFORMATION----
-* Use if helpful for the task.
-{% for file, text in aux_files.items() %}
---FILE: {{ file }}--
-{{ text.strip() }}
-{%- endfor -%}
-{%- endif -%}
+{% if aux_files %}
+----AUXILIARY INFORMATION----
+* Use if helpful for the task.
+{% for file, text in aux_files.items() %}
+--FILE: {{ file }}--
+{{ text.strip() }}
+{%- endfor -%}
+{%- endif -%}

gito/tpl/questions/changes_summary.j2

@@ -1,55 +1,55 @@
-{{ self_id }}
-----TASK----
-
-## Subtask 1:
-Write a codebase changes summary clearly describing and explaining it for the engineering managers.
-- It is intended to be posted into bug tracker for estimating work done in the pull request.
-- Summary should be in a form of compact changelist where each change is described by one sentence.
-- Caption should be: ## PR Summary: <3-10 words>
-- Each change summary BP list item should start from effort estimation icon:
-- - ◆◇◇ (up to 2 hours)
-- - ◆◆◇ (half day)
-- - ◆◆◆ (1-2 days and more)
-
-Also include this estimation legend below as "Pure Codebase Work Estimation Legend".
-
-
-## Subtask 1 (Issue alignment sentence)
-Include one sentence about how the code changes address the requirements of the associated issue listed below.
-- Use ✅ or ⚠️ to indicate whether the implementation fully satisfies the issue requirements.
-- Put this sentence immediately below the PR Summary title
-Examples:
-
-If the implementation fully delivers the requested functionality:
-```
-✅  Implementation Satisfies [<ISSUE_KEY>](<ISSUE_URL>).
-```
-If there are concerns about how thoroughly the code covers the requirements and technical description from the associated issue:
-```
-⚠️ <Describe specific gap or concern>.
-⚠️ <Describe additional limitation or missing feature>.
-```
-
-## Subtask 3:
-Write release notes for public documentation.
-- Caption should be: ## Release Notes Proposal
-Summarize the following changes, focusing on what is new, improved, or fixed for the end user.
-Do not include internal or technical details.
-Structure release notes using clear sections: Added, Changed, Fixed.
-Avoid internal technical jargon or developer-specific details.
-
-----RELATED CODEBASE CHANGES----
-{% for part in diff %}{{ part }}\n{% endfor %}
-
-----FULL FILE CONTENT AFTER APPLYING CHANGES----
-{% for file, file_lines in all_file_lines.items() %}
---FILE: {{ file }}--
-{{ file_lines }}
-{% endfor %}
-
-{%- if pipeline_out.associated_issue and pipeline_out.associated_issue.title %}
-----ASSOCIATED ISSUE----
-# {{ pipeline_out.associated_issue.title }}
-{{ pipeline_out.associated_issue.description }}
-URL: {{ pipeline_out.associated_issue.url }}
-{%- endif -%}{{ '\n' }}
+{{ self_id }}
+----TASK----
+
+## Subtask 1:
+Write a codebase changes summary clearly describing and explaining it for the engineering managers.
+- It is intended to be posted into bug tracker for estimating work done in the pull request.
+- Summary should be in a form of compact changelist where each change is described by one sentence.
+- Caption should be: ## PR Summary: <3-10 words>
+- Each change summary BP list item should start from effort estimation icon:
+- - ◆◇◇ (up to 2 hours)
+- - ◆◆◇ (half day)
+- - ◆◆◆ (1-2 days and more)
+
+Also include this estimation legend below as "Pure Codebase Work Estimation Legend".
+
+
+## Subtask 1 (Issue alignment sentence)
+Include one sentence about how the code changes address the requirements of the associated issue listed below.
+- Use ✅ or ⚠️ to indicate whether the implementation fully satisfies the issue requirements.
+- Put this sentence immediately below the PR Summary title
+Examples:
+
+If the implementation fully delivers the requested functionality:
+```
+✅  Implementation Satisfies [<ISSUE_KEY>](<ISSUE_URL>).
+```
+If there are concerns about how thoroughly the code covers the requirements and technical description from the associated issue:
+```
+⚠️ <Describe specific gap or concern>.
+⚠️ <Describe additional limitation or missing feature>.
+```
+
+## Subtask 3:
+Write release notes for public documentation.
+- Caption should be: ## Release Notes Proposal
+Summarize the following changes, focusing on what is new, improved, or fixed for the end user.
+Do not include internal or technical details.
+Structure release notes using clear sections: Added, Changed, Fixed.
+Avoid internal technical jargon or developer-specific details.
+
+----RELATED CODEBASE CHANGES----
+{% for part in diff %}{{ part }}\n{% endfor %}
+
+----FULL FILE CONTENT AFTER APPLYING CHANGES----
+{% for file, file_lines in all_file_lines.items() %}
+--FILE: {{ file }}--
+{{ file_lines }}
+{% endfor %}
+
+{%- if pipeline_out.associated_issue and pipeline_out.associated_issue.title %}
+----ASSOCIATED ISSUE----
+# {{ pipeline_out.associated_issue.title }}
+{{ pipeline_out.associated_issue.description }}
+URL: {{ pipeline_out.associated_issue.url }}
+{%- endif -%}{{ '\n' }}

gito/tpl/questions/release_notes.j2

@@ -1,26 +1,26 @@
-{{ self_id }}
-----TASK----
-Write release notes for public documentation.
-Summarize the following changes, focusing on what is new, improved, or fixed for the end user.
-Do not include internal or technical details.
-Structure release notes using clear sections: Added, Changed, Fixed.
-Avoid internal technical jargon or developer-specific details.
-
-
-----RELATED CODEBASE CHANGES----
-{% for part in diff %}{{ part }}\n{% endfor %}
-
-----FULL FILE CONTENT AFTER APPLYING CHANGES----
-{% for file, file_lines in all_file_lines.items() %}
---FILE: {{ file }}--
-{{ file_lines }}
-{% endfor %}
-
-{%- include "partial/aux_files.j2" -%}
-
-{%- if pipeline_out.associated_issue and pipeline_out.associated_issue.title %}
-----ASSOCIATED ISSUE----
-# {{ pipeline_out.associated_issue.title }}
-{{ pipeline_out.associated_issue.description }}
-URL: {{ pipeline_out.associated_issue.url }}
-{%- endif -%}{{ '\n' }}
+{{ self_id }}
+----TASK----
+Write release notes for public documentation.
+Summarize the following changes, focusing on what is new, improved, or fixed for the end user.
+Do not include internal or technical details.
+Structure release notes using clear sections: Added, Changed, Fixed.
+Avoid internal technical jargon or developer-specific details.
+
+
+----RELATED CODEBASE CHANGES----
+{% for part in diff %}{{ part }}\n{% endfor %}
+
+----FULL FILE CONTENT AFTER APPLYING CHANGES----
+{% for file, file_lines in all_file_lines.items() %}
+--FILE: {{ file }}--
+{{ file_lines }}
+{% endfor %}
+
+{%- include "partial/aux_files.j2" -%}
+
+{%- if pipeline_out.associated_issue and pipeline_out.associated_issue.title %}
+----ASSOCIATED ISSUE----
+# {{ pipeline_out.associated_issue.title }}
+{{ pipeline_out.associated_issue.description }}
+URL: {{ pipeline_out.associated_issue.url }}
+{%- endif -%}{{ '\n' }}

gito/tpl/questions/test_cases.j2

@@ -1,37 +1,37 @@
-{{ self_id }}
-----TASK----
-Create a concise list of manual QA test cases for the newly introduced codebase changes.
-The purpose of this document is to identify user journeys that could be disrupted by failures,
-cover security scenarios and edge cases, highlight potential risk areas introduced by the changes,
-and suggest focused testing to mitigate them.
-
-- Split the test cases into two categories:
-  - Critical
-  - Extended Coverage
-
-- Structure test cases using Markdown headers or bullet-point lists.
-
-- If the context includes the necessary details, describe the steps as thoroughly as possible—like for a junior QA
-  seeing this project for the first time.
-  If there are no details on how to perform a specific action, keep it abstract.
-  It is extremely important not to invent information.
-
-- Number test cases sequentially (C-01, C-02, E-01, E-02, etc.).
-
-----RELATED CODEBASE CHANGES----
-{% for part in diff %}{{ part }}\n{% endfor %}
-
-----FULL FILE CONTENT AFTER APPLYING CHANGES----
-{% for file, file_lines in all_file_lines.items() %}
---FILE: {{ file }}--
-{{ file_lines }}
-{% endfor %}
-
-{%- include "partial/aux_files.j2" -%}
-
-{%- if pipeline_out.associated_issue and pipeline_out.associated_issue.title %}
-----ASSOCIATED ISSUE----
-# {{ pipeline_out.associated_issue.title }}
-{{ pipeline_out.associated_issue.description }}
-URL: {{ pipeline_out.associated_issue.url }}
-{%- endif -%}{{ '\n' }}
+{{ self_id }}
+----TASK----
+Create a concise list of manual QA test cases for the newly introduced codebase changes.
+The purpose of this document is to identify user journeys that could be disrupted by failures,
+cover security scenarios and edge cases, highlight potential risk areas introduced by the changes,
+and suggest focused testing to mitigate them.
+
+- Split the test cases into two categories:
+  - Critical
+  - Extended Coverage
+
+- Structure test cases using Markdown headers or bullet-point lists.
+
+- If the context includes the necessary details, describe the steps as thoroughly as possible—like for a junior QA
+  seeing this project for the first time.
+  If there are no details on how to perform a specific action, keep it abstract.
+  It is extremely important not to invent information.
+
+- Number test cases sequentially (C-01, C-02, E-01, E-02, etc.).
+
+----RELATED CODEBASE CHANGES----
+{% for part in diff %}{{ part }}\n{% endfor %}
+
+----FULL FILE CONTENT AFTER APPLYING CHANGES----
+{% for file, file_lines in all_file_lines.items() %}
+--FILE: {{ file }}--
+{{ file_lines }}
+{% endfor %}
+
+{%- include "partial/aux_files.j2" -%}
+
+{%- if pipeline_out.associated_issue and pipeline_out.associated_issue.title %}
+----ASSOCIATED ISSUE----
+# {{ pipeline_out.associated_issue.title }}
+{{ pipeline_out.associated_issue.description }}
+URL: {{ pipeline_out.associated_issue.url }}
+{%- endif -%}{{ '\n' }}