bcgov / bcgov/wps

ASA Go: Automated Release Notes and Tags

Open
#5,232 0 comments 0 reactions 0 assignees View on GitHub
Task
Dominant language
Python
Stars
65
Forks
11
Avg merge
21h 25m
Merged PRs (30d)
70

Description

**Describe the task**
When the Android or iOS build workflows are triggered, automatically create a GitHub Release tagged `asa-go/v{version}` with auto-generated release notes scoped to ASA Go changes.

Any PR touching `mobile/asa-go/` gets labelled automatically. When a build workflow runs, a GitHub Release is created (or skipped if the tag already exists) with notes listing all merged ASA Go PRs since the previous release.

**Acceptance Criteria**
- [ ] Automated release notes created for both Android and iOS apps.
- [ ] When the Android or iOS build workflows are triggered, automatically create a GitHub Release tagged `asa-go/v{version}` .

**Additional context**
- [ ] Create `.github/actions/asa-go-release/action.yml` — reusable composite action that calls `gh release create with --generate-notes` targeting the build commit. Shared by both platform workflows.
- [ ] Add a `create-release` job to `asa_go_android_build.yml` that runs after a successful build and calls the action above.
- [ ] Add the release action call to `asa_go_ios_build_deploy.yml` after the IPA upload, before pushing to the App Store.
- [ ] Create `.github/labeler.yml` mapping `mobile/asa-go/**` → `asa-go` label, and `.github/workflows/labeler.yml` to apply it automatically on PRs.
- [ ] Create `.github/release.yml` to configure release note grouping — ASA Go PRs (via `asa-go` label) in their own section, dependency PRs excluded.
- [ ] Create the `asa-go` label in the repo (https://github.com/actions/labeler)

Contributor guide

Open the contributing guide

Research direction

Start by reading .github/workflows/asa_go_android_build.yml and .github/workflows/asa_go_ios_build_deploy.yml, then review the requested .github/actions/asa-go-release/action.yml, .github/labeler.yml, .github/workflows/labeler.yml, and .github/release.yml. Done means both successful build workflows create or skip the scoped asa-go release, PRs touching mobile/asa-go/ receive the label, and release notes group the relevant merged PRs while excluding dependencies.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, devops, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.