-
Notifications
You must be signed in to change notification settings - Fork 37
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
Flutter Support in Github Actions #375
Comments
We do have an example flutter project in this repo and it seems to work without anything special as far as I can tell. Have you tried upgrading |
I think there is a bug where it is grouping analyze steps that it thinks are identical into a single job - but it needs to separate them based on the SDK they use. |
cc @kevmoo |
Thanks for the reply @jakemac53 I made the upgrade from 6.1.0 to 6.2.0 and reran Let me also dive into how you have things set up in this repo for the flutter application because if thats the case I would have to assume that it is possible for me also. Maybe @kevmoo has some ideas in the meantime as well, lets see :) |
I have confirmed the issue is that So it is a bug. You can likely remove any |
One solution is to use |
Appreciate the help in the meantime! |
This is published now as version 6.2.1, please re-open if it doesn't resolve things |
I have a quick question that I wasn't sure if I was doing something wrong or this was a known issue.
I have a mixed repository (https://github.com/dropbear-software/fullstack-dart-demo) that contains:
I'm using
mono_repo
to mange all of this and when I runmono_repo presubmit
everything works find but on Github Actions it fails because it is downloading the Dart SDK rather than the Flutter SDK and when it comes to rundart pub upgrade
it will fail as can be seen here https://github.com/dropbear-software/fullstack-dart-demo/runs/5871740230?check_suite_focus=trueI just wanted to get a quick understanding if this was something that could be easily fixed on my end or it isn't a supported use case at the moment.
The text was updated successfully, but these errors were encountered: