Use cases

Jobs where this local tool earns its keep. Each names the role, the task before the deadline, the steps, and what done looks like.

1. Developer-machine admin upgrading a laptop fleet before Nov 30

Who: An IT / developer-machine admin responsible for Bitbucket OAuth laptops.

Task: Ensure every OAuth laptop reports GCM ≥ 3.0.0 before the block date.

Steps: Probe versions; use the home checklist with Windows fork where needed; push install.md steps; require a successful push smoke; collect Markdown exports.

Result: Fleet OAuth machines are upgraded; PAT-only machines documented as N/A.

2. CI engineer patching build images that git clone via GCM OAuth

Who: A CI engineer whose pipelines clone Bitbucket with GCM inside containers.

Task: Remove GCM < 3.0.0 from images or switch those jobs to PAT before Nov 30.

Steps: Inventory images/runners; answer axis B = ci; bump GCM or PAT; re-run a canary pipeline; attach export.

Result: No pipeline remains on vulnerable GCM OAuth versions.

3. Developer unblocking git push warnings after Atlassian notice

Who: An individual developer seeing post-push GCM upgrade warnings.

Task: Upgrade local GCM, clear cache, and confirm OAuth still works.

Steps: Answer the three axes; follow Windows direct-install if on GfW; reauth; keep the pack in a personal note.

Result: Warnings stop and push succeeds on GCM ≥ 3.0.0.