python-gitea 0.8.0__tar.gz → 0.10.0__tar.gz

{python_gitea-0.8.0 → python_gitea-0.10.0}/.github/workflows/codeql.yml

@@ -22,13 +22,13 @@ jobs:
               uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6
 
             - name: Initialize CodeQL
-              uses: github/codeql-action/init@5595ccaf912efad79be6eef63a5619ff05969be3 # v4
+              uses: github/codeql-action/init@ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd # v4
               with:
                   languages: python
                   queries: security-and-quality
 
             - name: Autobuild
-              uses: github/codeql-action/autobuild@5595ccaf912efad79be6eef63a5619ff05969be3 # v4
+              uses: github/codeql-action/autobuild@ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd # v4
 
             - name: Perform CodeQL Analysis
-              uses: github/codeql-action/analyze@5595ccaf912efad79be6eef63a5619ff05969be3 # v4
+              uses: github/codeql-action/analyze@ff2f1c621b7f889edc0d3c761ac2e6a3f8cdb0dd # v4

{python_gitea-0.8.0 → python_gitea-0.10.0}/.github/workflows/support_floor_update.yml

@@ -22,7 +22,7 @@ jobs:
 
             - name: Apply support policy (spec0, from pyproject tool table)
               id: policy
-              uses: isaac-cf-wong/dependency-support-policy-action@8cfabba7ba994cda4699cdbd0fbc7ede04dac145 # v0.2.3
+              uses: isaac-cf-wong/dependency-support-policy-action@7cce60e19b902747b4267c4f8e53820e3f3656ea # v0.2.4
               with:
                   mode: update
 

{python_gitea-0.8.0 → python_gitea-0.10.0}/.gitignore

@@ -133,3 +133,7 @@ dmypy.json
 
 # Node.js
 node_modules/
+
+# mutmut
+/mutants/
+/.mutmut-cache

{python_gitea-0.8.0 → python_gitea-0.10.0}/.pre-commit-config.yaml

@@ -16,7 +16,7 @@ repos:
           - id: check-json
 
     - repo: https://github.com/astral-sh/ruff-pre-commit
-      rev: v0.16.2
+      rev: v0.16.3
       hooks:
           - id: ruff
             args: [--fix, --config=pyproject.toml]
@@ -52,7 +52,7 @@ repos:
           - id: actionlint
 
     - repo: https://github.com/astral-sh/uv-pre-commit
-      rev: 0.12.3
+      rev: 0.12.5
       hooks:
           # Update the uv lockfile
           - id: uv-lock

{python_gitea-0.8.0 → python_gitea-0.10.0}/CONTRIBUTING.md

@@ -81,6 +81,80 @@ submitting a pull request—this guide will help you get started.
     pytest
     ```
 
+    Mutation testing runs the suite again for each deliberate alteration of the
+    source, and reports the alterations no test noticed:
+
+    ```shell
+    uv run mutmut run                  # every module
+    uv run mutmut run "gitea.cli.*"    # one subtree, while iterating
+    uv run mutmut results              # what survived
+    ```
+
+    A survivor is a change to the code that every test tolerated. Some cannot be
+    killed - a rewritten `typing.cast`, or anything in a `register_commands()`
+    that runs at import time - so read the diff `uv run mutmut show <mutant>`
+    prints before writing a test for one.
+
+    A filter selects which mutants are _run_, not which are written: every module
+    is mutated either way, so a scoped run still reports mutating the whole tree
+    and its progress counter reads `46/9042`, where the denominator counts every
+    mutant written and the numerator counts the ones the filter selected and
+    checked. Take the result of a scoped run from `uv run mutmut results` rather
+    than from that counter: it lists every mutant that was not killed, labelling
+    each as `survived` or as `not checked`, and naming the module it belongs to,
+    so the survivors of a scope are the `survived` entries whose names begin with
+    it. A filter matching no mutant stops the run with an error instead of
+    quietly widening it, so a scoped run that gets as far as testing is one that
+    scoped.
+
+    That listing names no killed mutant, though, so it cannot say how large the
+    scope was or what share of it died. Both are recorded per module, in the
+    `.meta` file mutmut writes beside each mutated module, whose
+    `exit_code_by_key` maps every mutant to the exit code of the run that checked
+    it - `0` survived, `1` killed, `null` never checked. Counting those gives the
+    verdict of a scope, and shows the modules outside it untouched. Point it at
+    the package directory the scope sits in - every module in the tree has a
+    `.meta`, so pointing it at the whole of `src/gitea` prints a line per module:
+
+    ```shell
+    uv run python - <<'PY'
+    import collections, json, pathlib
+
+    status = {0: "survived", 1: "killed", 3: "killed", 5: "no tests", 33: "no tests", None: "not checked"}
+    for meta in sorted(pathlib.Path("mutants/src/gitea/project").glob("*.py.meta")):
+        codes = json.loads(meta.read_text())["exit_code_by_key"]
+        counts = collections.Counter(status.get(c, f"exit {c}") for c in codes.values())
+        if counts:
+            print(f"{meta.name:24} {dict(counts)}")
+    PY
+    ```
+
+    ```text
+    async_project.py.meta    {'killed': 620, 'survived': 16}
+    base.py.meta             {'not checked': 215}
+    project.py.meta          {'killed': 620, 'survived': 16}
+    ```
+
+    That is the output of a run scoped to the two project resource modules: 636
+    mutants each, 1,240 of the 1,272 killed, and the 215 of a module outside the
+    scope sitting unchecked. Start from `rm -rf mutants` when a run has to stand
+    on its own, since the verdicts of one run are otherwise carried into the
+    next.
+
+    To scope what is _written_ as well, and get a counter whose denominator is
+    the scope, point `source_paths` at the modules and let `also_copy` carry the
+    rest of the package that the tests import. Scoped to the same two modules as
+    above, that run reports mutating two files and counts `1272/1272`:
+
+    ```toml
+    [tool.mutmut]
+    source_paths = [
+      "src/gitea/project/project.py",
+      "src/gitea/project/async_project.py",
+    ]
+    also_copy = ["scripts/", "src/"]
+    ```
+
 8. Open a Pull Request
 
     Clearly describe the motivation and scope of your change. Link it to the relevant issue if applicable.

{python_gitea-0.8.0 → python_gitea-0.10.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: python-gitea
-Version: 0.8.0
+Version: 0.10.0
 Summary: A Python package for interacting with the Gitea API, offering a simple interface to access repositories, users, organizations, issues, and more for automation and data management.
 Project-URL: Documentation, https://isaac-cf-wong.github.io/python-gitea
 Project-URL: Source, https://github.com/isaac-cf-wong/python-gitea

{python_gitea-0.8.0 → python_gitea-0.10.0}/docs/dev/architecture.md

@@ -44,6 +44,7 @@ src/gitea/
 ├── milestone/               # Milestone resource (sync + async)
 ├── notification/            # Notification resource (sync + async)
 ├── project/                 # Project resource (sync + async)
+├── organization/            # Organization resource (sync + async)
 ├── cli/                     # Typer CLI application
 │   ├── main.py              # gitea-cli entry point, command registration
 │   ├── config/              # config commands
@@ -54,10 +55,14 @@ src/gitea/
 │   ├── milestone/           # milestone commands
 │   ├── notification/        # notification commands
 │   ├── project/             # project, column, and project-issue commands
+│   ├── organization/        # org commands
+│   ├── repository/          # repo commands
 │   ├── user/                # user commands
 │   └── utils/               # auth resolution, API helpers, conversions
-└── utils/                   # Logging and response helpers
+└── utils/                   # Logging, field names, pagination, and response helpers
+    ├── fields.py            # Field-name convention and compatibility aliases
     ├── log.py               # Logger setup
+    ├── pagination.py        # Paginated-listing walkers
     └── response.py          # Response processing helpers
 ```
 
@@ -84,6 +89,7 @@ with Gitea(token="...", base_url="...") as client:
     client.milestone      # Milestone
     client.notification   # Notification
     client.project        # Project
+    client.organization   # Organization
 ```
 
 ## Resource Layer
@@ -96,6 +102,11 @@ names. Methods map one-to-one onto Gitea REST endpoints and return either:
   JSON payload and `status` carries metadata such as the HTTP status code, or
 - the raw HTTP response for mutating operations.
 
+Work that spans several endpoints lives beside the resource rather than inside
+it, so the resource methods stay one-to-one with the API. For example,
+`gitea.issue.project_column` resolves the board column an issue's card sits in,
+which Gitea only reveals through the project's column listings.
+
 ## CLI Layer
 
 The CLI is a single Typer application registered in `cli/main.py`. Each resource