Skip to content

Publish maintained fork with integrated Docs workflow improvements - #10

Merged
ratovarius merged 19 commits into
mainfrom
chore/publish-maintained-fork
Sep 11, 2026
Merged

ratovarius merged 19 commits into
mainfrom
chore/publish-maintained-fork

Conversation

@ratovarius

Copy link
Copy Markdown
Owner

Result

Make ratovarius/cli:main the maintained public fork containing the reviewed Google Docs workflow improvements. The fork remains natively linked to googleworkspace/cli; original history, authorship, copyright notices, and Apache-2.0 licensing are preserved.

The README now installs this fork from source and identifies its maintainer. FORK.md links every improvement to its issue and focused upstream PR. CONTRIBUTING.md documents fork-local development, clean upstream submissions, and reviewed upstream syncs. CLI help and shared agent guidance route fork feedback here while retaining upstream attribution.

Integrated contributions

Improvement Fork issue Focused upstream PR
Explicit fields absent from Discovery #1 googleworkspace#931
Structured Google Docs reader #2 googleworkspace#932
Revision-bound reviewed text patches #3 googleworkspace#933
Visual review bundles #4 googleworkspace#934
Trusted file root for exports/uploads #5 googleworkspace#935
Credential-free request previews #6 googleworkspace#936
Preserve credentials on decryption failure #7 googleworkspace#937
Current Clippy compatibility #8 googleworkspace#930

The upstream branches/PRs remain separate and open. This PR integrates them here; it does not assert upstream acceptance. A pristine upstream-main branch records the imported original main.

Independent maintenance

  • Add pinned, read-only Rust tests/builds on Linux/macOS plus formatting/Clippy, alongside the two existing Python companion workflows.
  • Preserve eleven inherited upstream workflows unchanged under .github/upstream-workflows/, where Actions does not execute them. Those jobs assume Google-owned bots, publishing destinations, live accounts, or policies. The archive README documents the smaller initial fork CI scope.
  • Assign fork review ownership and enable private vulnerability reporting; remove inherited promises of a Google security-team response.
  • Publish source on GitHub. Upstream package names/version are retained for compatibility; fork binaries and owned registry namespaces require a separate release task.

Validation

  • Fresh local workspace tests: 860 Rust tests (95 library, 739 CLI unit, 22 dry-run/fixture, 4 file-root subprocess tests).
  • 36 reviewed-patch tests and 50 review-bundle tests, including the actual built CLI export regression: 946 tests total.
  • cargo fmt --all -- --check, cargo clippy --workspace --locked -- -D warnings, and cargo build --workspace --locked passed.
  • Corrected an intermittent synthetic HTTP trap: explicitly block accepted sockets and consume Content-Length bodies before closing. A new split-body regression failed before the fix and passed afterward, including 20 repeated executions. The test-only correction is also included in upstream PR fix(auth): validate request dry-runs without credentials googleworkspace/cli#936.
  • Independent reviews approved the integration and publication; both publication follow-up findings were corrected. Active workflows parsed; all eleven archived workflows matched upstream byte for byte. Built CLI help and generated/reference support guidance agree.
  • Tests use synthetic fixtures and loopback servers. No real Google document or stored account credentials were used. This does not validate live Google APIs, preview enrollment, real locked-keyring behavior, Windows, or the full upstream release matrix.

Fixes #1
Fixes #2
Fixes #3
Fixes #4
Fixes #5
Fixes #6
Fixes #7
Fixes #8
Fixes #9

@ratovarius

Copy link
Copy Markdown
Owner Author

The publication branch passed fresh local validation (946 tests, format, strict Clippy and build) and independent review. The three maintained fork workflows are now running on this PR.

An inherited Automation job ran once from the old base branch via pull_request_target. Its File Labeler failed with Parameter token or opts.auth is required because it expects GOOGLEWORKSPACE_BOT_TOKEN. That obsolete workflow has been disabled in repository settings and is moved unchanged to the inactive workflow archive in this PR. It is not a failing application test. The old run is retained as history; the maintained fork checks are Fork CI, Docs Review Example, and Docs Review Bundle.

@ratovarius
ratovarius merged commit a25acfc into main Sep 11, 2026
10 of 11 checks passed
@ratovarius

Copy link
Copy Markdown
Owner Author

Published main at a25acfc6ffda1b9b46879dd498c795598078276f has now passed all seven maintained checks again:

The published tree exactly matches the locally validated tree (946 tests). GitHub confirms public visibility and the native googleworkspace/cli fork parent. Issues #1#9 are closed, and upstream PRs googleworkspace#930googleworkspace#937 remain open for review. The three workflows above are the only active workflows on the maintained main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment