Q42 / Q42/Template.ComposeMultiplatform
Change firebase-app-distribution-action to something more recent
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 7d 15h
- Merged PRs (30d)
- 15
Description
From Kseniia:
nickwph/firebase-app-distribution-action is a 3rd party Action. The author hasn't updated it in three years - and I'm always a bit hesitant to add 3rd party Actions because they have access to the code and secrets in the workflow they are running inside of.
The Firebase CLI is pre-installed on our runners, so that's possible to use:
https://firebase.google.com/docs/app-distribution/android/distribute-cli?apptype=aab
Or uploading via Gradle:
https://firebase.google.com/docs/app-distribution/android/distribute-gradle?apptype=aab
We also have a repository of our own Q42 actions here. So it's also possible (if it requires a lot of YAML/code) to create a custom action that is shared across projects there:
https://github.com/Q42/actions
Contributor guide
No contributing guide indexed for this repository
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
Locate the GitHub Actions workflow that invokes nickwph/firebase-app-distribution-action and read how the Android bundle is built and distributed. Compare the Firebase CLI and Gradle distribution approaches described in the linked documentation, while considering whether a shared Q42 action is needed. Done means the outdated third-party action is replaced and app distribution still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kotlin, yaml
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100