Sync Github Action's Workflow Files Across Repositories
- Add Fastlane to the destination repository by copying the
example
folder from the fastlane repository and configure the .env files and code signing accordingly (follow this guide for the complete process). - Copy the example .env file to the destination repository inside the
.github/workflows/
folder. Update it to match your project setings. - Ensure the account
levinriegner-qa
has write access to the destination repository. - Add the destination repository to keep in sync inside the
REPOSITORIES
variable on the workflow-sync.yml file. - Push the file changes to master.
- Approve the auto-generated Pull Request in the destination repository.
To create a new internal release use the GitHub Actions Internal
Flow:
- Checkout from
master
to a new branch namedinternal/a.b.c
and push to origin.- Android: Build is uploaded to Firebase App Tester.
- iOS: Build is uploaded to Testflight.
To create a new release use the GitHub Actions Release
Flow:
- Checkout from
master
to a new branch namedrelease/a.b.c
and push to origin. - Once both platforms are finished, visit their store portals to submit the builds.
- Android: Build is uploaded to Production track as Draft.
- iOS: Build is uploaded to Testflight.
Commits to master
will execute all Flutter Unit Tests.
If you need to upload a new build for the same internal release, first push the changes to master and then rebase/merge them on top of the internal branch.
Additional builds cannot be sent for the same production release. Simply create a new release branch increasing the version name.
Workflows that include the workflow_dispatch:
trigger can also be dispatched manually on the GitHub website:
- Navigate to the "Actions" tab on the repository.
- Select the "Workflow" you want to trigger.
- Press the "Run workflow" button.
- Select the branch you want to run it from.
- Press "Run workflow".
- Update the workflows inside the
workflows
folder as needed. - (Optional) Test your changes on the
testbed
branch. - Push changes to
master
to trigger the sync workflow. - Approve the auto-generated Pull Request in the destination repositories.