actions / actions/starter-workflows
name: Build Flutter APK on: push: branches: - main jobs: build: name: Build APK runs-on: ubuntu-latest steps: - name: Checkout source code uses: actions/checkout@v3 - name: Set up 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: Up
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.1k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
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 title contains a proposed GitHub Actions workflow using actions/checkout@v3, subosito/flutter-action@v2, flutter pub get, and flutter build apk --release. First clarify which starter workflow or repository change is intended, then inspect existing workflow templates; done should mean the requested Flutter APK workflow is clearly defined and validated, but no test or target file is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flutter, github-actions
- Domain
- build-system, ci-cd, mobile
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100