Mobile - Add expo workflow yaml for allowing devs to trigger manual builds #349
Conversation
| default: "development" | ||
| type: choice | ||
| # Should match the ones in `eas.json` | ||
| options: |
There was a problem hiding this comment.
this goes nicely with my open PR as well that creates dynamic review app based builds.
I think dynamically adding them to the eas.json like this allows us to create unique builds. In this case as you have it, each engineer's build will overwrite the others (although at this moment many of us don't really need builds that often).
I also wonder if this can be avoided by removing the channel arg
There was a problem hiding this comment.
I mean initially I wrote this because I happened not to have enough permissions in a project to use the eas cli myself so I just used the action to get a build I needed.
This as you said is not something that we would use often, it is just a convenience, mostly to get development builds that we usually need when we deviate from expo go.
| with: | ||
| expo-version: latest | ||
| eas-version: latest | ||
| token: ${{ secrets.EXPO_TOKEN }} |
There was a problem hiding this comment.
@lakardion - Cookiecutter is trying to render this and failing to 'bake'.
What this does
With this any dev in the repo can create builds following any given profile from
eas.jsonThis allows to easily create development builds or staging builds without the need of the dev to have to go through eas CLI in the local.
How to test
Add user steps to achieve desired functionality for this feature.