Skip to content

fix: using community cli explicitly #10

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

Merged
merged 2 commits into from
Aug 15, 2024
Merged

Conversation

blakef
Copy link
Contributor

@blakef blakef commented Aug 15, 2024

I think this will be resolved by calling the community cli directly:

CleanShot 2024-08-15 at 16 26 44@2x

@blakef
Copy link
Contributor Author

blakef commented Aug 15, 2024

^ will fail because we need to run the action. I can also just run it and commit to fix things.

@blakef blakef force-pushed the fix/move-to-community-cli branch from d92e710 to e88a748 Compare August 15, 2024 15:31
@@ -32,7 +32,7 @@ jobs:
if: steps.yarnoutdated.outcome == 'failure'
run: |
rm -rf ReproducerApp
npx react-native@latest init ReproducerApp --skip-install --skip-git-init
npx @react-native-community/cli@latest init ReproducerApp --skip-install --skip-git-init
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the significant change, the rest is me just running the rest of this workflow to get the project back into a good state.

@blakef blakef requested a review from cortinico August 15, 2024 15:33
@cortinico cortinico merged commit 0d882b0 into main Aug 15, 2024
2 checks passed
@cortinico cortinico deleted the fix/move-to-community-cli branch August 15, 2024 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants