Manusで任意のスキルを実行
ワンクリックで
ワンクリックで
ワンクリックでManusで任意のスキルを実行
始める$pwd:
github-workflows
// Manage and automate Android CI/CD workflows using GitHub Actions in this repository.
$ git log --oneline --stat
stars:323
forks:59
updated:2026年4月24日 04:02
SKILL.md
// Manage and automate Android CI/CD workflows using GitHub Actions in this repository.
| name | github-workflows |
| description | Manage and automate Android CI/CD workflows using GitHub Actions in this repository. |
This skill provides instructions for managing, extending, and troubleshooting the GitHub Actions workflows in the automated-build-android-app-with-github-action project.
The repository contains several workflows located in .github/workflows/:
android-ci-generate-apk-aab-upload-push-github.yml: Builds APK/AAB and pushes the results to the buildActionResult folder in the repository.android-ci.yml: Basic CI for building and testing.android-ci-generate-apk-aab-upload.yml: Builds and uploads artifacts to GitHub Actions.android-ci-generate-apk-aab-download.yml: Research workflow for downloading artifacts.android-ci-publish-play-store.yml: (In research) Template for publishing to Google Play Store.Each workflow uses common environment variables defined at the top of the file:
main_project_module: Usually app.playstore_name: Display name for the app (e.g., Frogobox ID).build_output_path: Directory where build results are stored (e.g., buildActionResult).To add a new Gradle task to a workflow, insert a new step in the jobs.build.steps section:
- name: Your Task Name
run: ./gradlew yourTaskName
If you want to change where the APKs/AABs are pushed in the repository, update the build_output_path env variable.
release/** branches.workflow_dispatch to trigger manually from the GitHub Actions tab../gradlew has execution permissions (chmod +x ./gradlew).SIGN_KEY, ALIAS, STORE_KEY_PASSWORD, and KEY_PASSWORD.