-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI / Guthub actions v2 #66
Conversation
* ADD github actions v2
#68) ADD CI firebase upload ADD CI unittests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good, thanks!
None of my comments are blocking, so I'll approve.
But please do consider them :-)
|
||
- First create your own keystore and store it in 1pw. _You do not add this keystore to the repo_ ( | ||
like we did in this template as an example). | ||
- add a KEYSTORE_BASE_64 [new github repository secret](./settings/secrets/actions/new) that is the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After merging this PR, please trigger ask dependabot build by choosing any open dependabot PR and reacting with @dependabot recreate
If that fails, the changes you made in the secrets need to be reflected into the dependabot secrets; and that should be documented here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this important?
We had a two-headed CI setup, partly fastlane, partly github actions. It increased complexity * 2. Also, signing key usage was not included, we've added it here.
In this ticket
devDebug
apk and aprodDebug
apk buildprodRelease
bundle andprodRelease
apk)Example actions that ran because of this PR: