gplay-migrate-fastlane

Migrates Fastlane supply metadata directories to gplay CLI format for Google Play management.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/lettucebo/Skills --skill gplay-migrate-fastlane-lettucebo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gplay-migrate-fastlane
Source: https://github.com/lettucebo/Skills/tree/main/skills/google-play-console-cli/gplay-migrate-fastlane
Command: npx skills add https://github.com/lettucebo/Skills --skill gplay-migrate-fastlane-lettucebo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams moving away from Fastlane supply need to convert their existing Play Store metadata directory structure into the format used by the gplay CLI, without manually reorganizing titles, descriptions, changelogs, and images for every locale. ## Core Features & Use Cases - Directory Conversion: Converts Fastlane metadata files (title.txt, short_description.txt, full_description.txt, video.txt) into gplay's consolidated listing.json format while copying changelogs and images as-is. - Selective Migration: Supports dry-run previews and locale filtering so you can migrate and verify one locale at a time before committing. - Command Mapping: Provides direct equivalents for Fastlane supply commands (init, upload, track rollout) using gplay sync and release commands. - Use Case: A team replacing Fastlane in their CI/CD pipeline runs a dry-run migration, verifies the output structure, then imports the converted metadata to the Play Store with gplay sync import-listings. ## Quick Start Ask the AI to migrate your Fastlane metadata directory at ./fastlane/metadata/android into gplay format, starting with a dry run to preview the output.

Frequently Asked Questions about gplay-migrate-fastlane

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate from Fastlane supply to gplay CLI?▼

Run gplay migrate fastlane with --source pointing to your Fastlane metadata directory and --output-dir for the converted output. Preview first with --dry-run, then verify the output and import it using gplay sync import-listings.

What is the gplay equivalent of fastlane supply commands?▼

fastlane supply init maps to gplay sync export-listings, and fastlane supply maps to gplay sync import-listings. Track releases like fastlane supply --track beta correspond to gplay release --track beta --bundle app.aab.

Can I migrate only specific locales from Fastlane metadata?▼

Yes, use the --locales flag with a comma-separated list such as en-US,es-ES,fr-FR. Without the flag, all locales in the source directory are migrated by default.

Does the Fastlane to gplay migration change my changelog or image files?▼

No, changelogs and images are copied as-is during migration. Only the text files (title, short description, full description, video) are consolidated into a single listing.json per locale.

How do I preview a Fastlane migration without writing files?▼

Add the --dry-run flag to the gplay migrate fastlane command. This previews the migration output without writing any files, which is also useful for CI validation by checking the exit code.