Automatize Release Work
Open
Nobody has claimed this yet.
Feature request
QA
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
Automatize release work:
- Sign tag (GPG common key?)
- Build release APK
- Build release Bundle
- Deploy to GPlay
Additional (N2H):
- Screenshots (README, fdroid, GPlay)
- Calens
- Generate release in GitHub
TASKS
- Research (if needed)
- Create branch feature/feature_name
- Development tasks
- Implement whatever
- ...
- Code review and apply changes requested
- Design test plan
- QA
- Merge branch feature/feature_name into master
PR
- App
- Library (if needed)
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
Start by mapping the requested release steps: GPG tag signing, release APK and Bundle builds, Google Play deployment, and GitHub release generation. Treat screenshots and calendar-related items as additional scope, and define completion separately for each release artifact and destination.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- build-system, mobile, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100