Github Actions

by callstackincubator61e6e7dfdf3aMIT1.6K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

GitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts. Use when setting up CI build pipelines or downloading GitHub Actions artifacts via gh CLI and GitHub API.

Instructions onlyDevOps & Cloud
AI-generated overview

Provides GitHub Actions workflow patterns for building React Native iOS simulator and Android emulator artifacts in CI.

What it does
This skill supplies reusable GitHub Actions patterns for building React Native apps for iOS simulators and Android emulators in the cloud, then publishing the resulting artifacts. It covers composite actions for iOS .app.tar.gz and Android .apk builds, workflow wiring, and artifact upload with actions/upload-artifact@v4. It also documents retrieving artifacts by ID or name using the gh CLI or the GitHub REST API.
When to use it
Use it when creating CI workflows that build React Native simulator or emulator artifacts, or when uploading iOS simulator and Android emulator installables from pull requests or manual dispatch runs. It also fits cases where local-only mobile builds should be replaced by downloadable CI artifacts with stable IDs for scripted retrieval.
Requirements
Requires GitHub Actions as the CI environment, the gh CLI or GitHub API access for artifact download, and network access to GitHub. The skill ships no scripts; it is instructions plus reference markdown files.

GitHub Actions Build Artifacts

Overview

Reusable GitHub Actions patterns to build React Native apps for iOS simulators and Android emulators in the cloud, then publish artifacts retrievable via gh CLI or GitHub API.

When to Apply

Use this skill when:

  • Creating CI workflows that build React Native simulator/emulator artifacts.
  • Uploading iOS simulator and Android emulator installables from PRs or manual dispatch runs.
  • Replacing local-only mobile builds with downloadable CI artifacts.
  • Needing stable artifact IDs/names for scripted retrieval with gh or REST API.

Quick Reference

  1. Add composite actions from gha-ios-composite-action.md [blocked] and gha-android-composite-action.md [blocked].
  2. Wire them into .github/workflows/mobile-build.yml from gha-workflow-and-downloads.md [blocked].
  3. Upload with actions/upload-artifact@v4 and capture artifact-id output.
  4. Download with gh run download or GET /repos/{owner}/{repo}/actions/artifacts/{artifact_id}/{archive_format}.

References

FileDescription
gha-ios-composite-action.md [blocked]Composite action.yml for iOS simulator .app.tar.gz builds and artifact upload
gha-android-composite-action.md [blocked]Composite action.yml for Android emulator .apk builds and artifact upload
gha-workflow-and-downloads.md [blocked]End-to-end workflow wiring plus gh and REST download commands

Problem -> Skill Mapping

ProblemStart With
Need CI iOS simulator .app.tar.gz artifactgha-ios-composite-action.md [blocked]
Need CI Android emulator .apk artifactgha-android-composite-action.md [blocked]
Need one workflow to trigger both platform jobsgha-workflow-and-downloads.md [blocked]
Need scripted artifact downloadgha-workflow-and-downloads.md [blocked]

Source Inspiration

Source and attribution

Source:callstackincubator/agent-skillsinskills/github-actionsat commit61e6e7d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal