Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[continuous-deploy-fingerprint] Update readme for prerequisistes #304

Merged
merged 1 commit into from
Sep 16, 2024
Merged

[continuous-deploy-fingerprint] Update readme for prerequisistes #304

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions continuous-deploy-fingerprint/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
<div align="center">
<h1>continuous-deploy-fingerprint</h1>
<p>Continuously deploys an Expo project using EAS Build and EAS Update in combination with fingerprint runtime versions</p>
<p>Continuously deploys an Expo project using EAS Build and EAS Update in combination with a fingerprint runtime version</p>
</div>

<p align="center">
Expand Down Expand Up @@ -40,10 +40,15 @@
`continuous-deploy-fingerprint` is a GitHub Action continuously deploys an Expo project using the expo-updates fingerprint runtime version policy. When run, it performs the following tasks in order, once for each platform:
1. Check current fingerprint of the project.
2. Check for EAS builds with specified profile matching that fingerprint.
3. If an EAS build doesn't exist, start one.
3. If a in-progress or finished EAS build doesn't exist, start one.
4. Publish an update on EAS update.
5. If run on a PR, post a comment indicating what was done.

### Prerequisites

- Project must have expo-updates and EAS Update set up.
- Must have run the builds at least once manually in order to configure credentials. This can be done by running `eas build --profile <profile> --platform <platform>` for each profile and platform you have set up for this action.

### Configuration options

This action is customizable through variables defined in the [`action.yml`](action.yml).
Expand Down
Loading