swiftlang / swiftlang/github-workflows
.github/workflows/build_apk.yml
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 115
- Forks
- 57
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 3
Description
name: Build Flutter APK
on:
push:
branches: [ main ]
pull_request:
branches: [ main ]
jobs:
build:
name: Build APK
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v3
- name: Setup Flutter
uses: subosito/flutter-action@v2
with:
flutter-version: '3.13.0'
- name: Install dependencies
run: flutter pub get
- name: Build APK
run: flutter build apk --release
- name: Upload APK
uses: actions/upload-artifact@v3
with:
name: snabbit-apk
path: build/app/outputs/flutter-apk/app-release.apk
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The proposed workflow is in .github/workflows/build_apk.yml; start by checking the repository's Flutter setup and whether the listed Flutter version and artifact path match it. Run the workflow's commands, including flutter pub get and flutter build apk --release. Done means the GitHub Actions job completes and uploads the snabbit-apk artifact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flutter, github-actions
- Domain
- ci-cd, mobile
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100