polygit 0.3.3__tar.gz → 0.3.4__tar.gz

polygit-0.3.4/.github/workflows/ci.yml

@@ -0,0 +1,42 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+    tags: ["v*.*.*"]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v3
+      - run: uv sync
+      - run: uv run pytest
+
+  build:
+    needs: test
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v3
+      - run: uv build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  deploy:
+    needs: build
+    if: startsWith(github.ref, 'refs/tags/v')
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v3
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - run: uv publish --token ${{ secrets.PYPI_API_TOKEN }}

{polygit-0.3.3 → polygit-0.3.4}/AGENTS.md

@@ -8,8 +8,8 @@ manages multiple git repos (across GitHub/GitLab, multiple orgs/namespaces) from
 very `~/development/gitlab` tree these AGENTS.md files live in.
 
 Standard `src`-layout Python package (`pyproject.toml`, `uv.lock` — uses `uv`, not
-pip/poetry, for dev dependency management). `.gitlab-ci.yml` presumably builds/publishes on
-tag, mirroring `gitlab-ci-generator`'s pattern.
+pip/poetry, for dev dependency management). Hosted on GitHub (moved from GitLab); CI is
+`.github/workflows/ci.yml` — test on every push/PR, build+publish to PyPI on `v*.*.*` tags.
 
 Replaced an older `sync.sh` script (see recent commit history) — if you find references to
 `sync.sh` elsewhere in the user's dotfiles/bootstrap scripts, they're stale.

{polygit-0.3.3 → polygit-0.3.4}/PKG-INFO

@@ -1,8 +1,8 @@
 Metadata-Version: 2.4
 Name: polygit
-Version: 0.3.3
+Version: 0.3.4
 Summary: Manage multiple git repos from a single .pgit config file.
-Project-URL: Repository, https://gitlab.com/gary.schaetz/public/polygit
+Project-URL: Repository, https://github.com/gschaetz/polygit
 Author-email: Gary Schaetz <gary@schaetzkc.com>
 License: MIT License
         

{polygit-0.3.3 → polygit-0.3.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "polygit"
-version = "0.3.3"
+version = "0.3.4"
 description = "Manage multiple git repos from a single .pgit config file."
 readme = "README.md"
 license = { file = "LICENSE.txt" }
@@ -16,7 +16,7 @@ dependencies = [
 ]
 
 [project.urls]
-Repository = "https://gitlab.com/gary.schaetz/public/polygit"
+Repository = "https://github.com/gschaetz/polygit"
 
 [project.scripts]
 pgit = "polygit.cli:main"

polygit-0.3.3/.gitlab-ci.yml

@@ -1,57 +0,0 @@
-include:
-  - project: "gary.schaetz/private/pipelines"
-    ref: main
-    file: 'templates/rules/rules.yml'
-
-stages:
-  - test
-  - build
-  - deploy
-
-variables:
-  UV_NO_SYNC: "0"
-
-test:
-  image: gschaetz/python:latest
-  stage: test
-  tags:
-    - docker
-    - kubernetes
-  # Explicit rules instead of relying on GitLab's implicit default (only: [branches, tags]):
-  # that default happens to exclude merge_request_event already, but making it explicit here
-  # matches the pattern every other repo running on these self-hosted runners uses, rather
-  # than depending on undocumented default behavior for a job that runs arbitrary repo code.
-  rules:
-    - !reference [.job_rules, standard-rule]
-    - !reference [.job_rules, manual-rule]
-    - !reference [.job_rules, schedule-rule]
-  script:
-    - uv sync
-    - uv run pytest
-
-build:
-  image: gschaetz/python:latest
-  stage: build
-  tags:
-    - docker
-    - kubernetes
-  rules:
-    - if: $CI_COMMIT_TAG =~ /^v\d+\.\d+\.\d+$/
-  script:
-    - uv build
-  artifacts:
-    paths:
-      - dist/
-
-deploy:
-  image: gschaetz/python:latest
-  stage: deploy
-  tags:
-    - docker
-    - kubernetes
-  rules:
-    - if: $CI_COMMIT_TAG =~ /^v\d+\.\d+\.\d+$/
-  dependencies:
-    - build
-  script:
-    - uv publish --token $PYPI_API_TOKEN