gpd-betagroups
Scannednpx machina-cli add skill rudrankriyam/app-store-connect-cli-skills/gpd-betagroups --openclawFiles (1)
SKILL.md
1.1 KB
GPD Beta Groups
Use this skill when managing beta testers, groups, and build distribution on Google Play.
List and manage testers
gpd publish testers list --package com.example.app --track internal
gpd publish testers list --package com.example.app --track beta
gpd publish testers add --package com.example.app --track internal --group testers@example.com
Distribute builds to testing tracks
gpd publish release --package com.example.app --track internal --status completed
gpd publish release --package com.example.app --track beta --status completed
Promote between testing tracks
gpd publish promote --package com.example.app --from-track internal --to-track beta
gpd publish promote --package com.example.app --from-track beta --to-track production
Notes
- Use
--track internalfor fast internal distribution. - Prefer IDs for deterministic operations; use the ID resolver skill when needed.
Source
git clone https://github.com/rudrankriyam/app-store-connect-cli-skills/blob/main/skills/gpd-betagroups/SKILL.mdView on GitHub Overview
This skill lets you manage Google Play beta testers, tester groups, and build distribution using the gpd CLI. It covers listing and adding testers, distributing releases to internal and beta tracks, and promoting builds across tracks.
How This Skill Works
You manage testers and groups with gpd publish testers (list/add) for a package and track. You distribute builds with gpd publish release to a track, then promote between tracks with gpd publish promote. The notes indicate using --track internal for fast internal distribution and using IDs for deterministic operations when needed.
When to Use It
- Onboard and manage internal testers for rapid feedback.
- Distribute a build to the internal track for quick validation before broad beta rollout.
- Publish and manage testers for the beta track to external testers.
- Promote builds from internal to beta, and from beta to production during rollout.
- Organize testers by groups and leverage IDs for deterministic operations when needed.
Quick Start
- Step 1: List testers for your package and internal track (gpd publish testers list --package your.pkg --track internal).
- Step 2: Add testers to the internal group (gpd publish testers add --package your.pkg --track internal --group tester@example.com).
- Step 3: Publish a release and promote to the next track (gpd publish release --package your.pkg --track internal --status completed && gpd publish promote --package your.pkg --from-track internal --to-track beta).
Best Practices
- Use --track internal for fast internal distribution.
- Prefer IDs for deterministic operations; use the ID resolver skill when needed.
- Keep tester groups small and well-documented to avoid misconfigurations.
- Verify --status completed when publishing releases to ensure distribution occurs.
- Test changes with a staging package name before pushing to production.
Example Use Cases
- List internal testers: gpd publish testers list --package com.example.app --track internal
- Add testers to internal: gpd publish testers add --package com.example.app --track internal --group testers@example.com
- Distribute a build to internal: gpd publish release --package com.example.app --track internal --status completed
- Promote internal to beta: gpd publish promote --package com.example.app --from-track internal --to-track beta
- Promote beta to production: gpd publish promote --package com.example.app --from-track beta --to-track production
Frequently Asked Questions
Add this skill to your agents