Productionize: tests, CLI, CI/CD, self-update #1

2026-07-03T13:55:16Z

KofTwentyTwo commented

2026-07-03 13:55:16 +00:00

(Migrated from github.com)

Integrates the productionize agent workflow output:

Tests: 15 real-git integration tests (local fixture repos, no network) — 35 total, engine coverage 60.6%
CLI: gclo.Cli scriptable head (sync/orgs, --json, exit codes, secure token sourcing) — verified against live GitHub
Self-update: Velopack 1.2.0 (custom Main, UpdateService, Help menu check/update flow)
CI/CD: CI with warnaserror/tests/coverage/format gates, CodeQL, dependency review, Dependabot, tag-driven release pipeline (Velopack installer + CLI zip + gated NuGet/winget)

Local verification: build 0 warnings, 35/35 tests, format gate clean, GUI launch through the new entry point, live e2e smoke (clone + pull) against MMLT-Holdings.

🤖 Generated with Claude Code

Integrates the productionize agent workflow output: - **Tests**: 15 real-git integration tests (local fixture repos, no network) — 35 total, engine coverage 60.6% - **CLI**: `gclo.Cli` scriptable head (sync/orgs, `--json`, exit codes, secure token sourcing) — verified against live GitHub - **Self-update**: Velopack 1.2.0 (custom Main, UpdateService, Help menu check/update flow) - **CI/CD**: CI with warnaserror/tests/coverage/format gates, CodeQL, dependency review, Dependabot, tag-driven release pipeline (Velopack installer + CLI zip + gated NuGet/winget) Local verification: build 0 warnings, 35/35 tests, format gate clean, GUI launch through the new entry point, live e2e smoke (clone + pull) against MMLT-Holdings. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

github-advanced-security[bot] commented

2026-07-03 14:47:52 +00:00

(Migrated from github.com)

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. ### What Enabling Code Scanning Means: - The 'Security' tab will display more code scanning analysis results (e.g., for the default branch). - Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. - You will be able to see the analysis results for the pull request's branch on this [overview](/KofTwentyTwo/gclo/security/code-scanning?query=pr%3A1+is%3Aopen) once the scans have completed and the checks have passed. For more information about GitHub Code Scanning, check out [the documentation](https://docs.github.com/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning).

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#1