-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat: Add a GitHub Actions workflow for use in CI workflows #339
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution! A few adjustments are needed but this is a good addition!
- name: Install ${{ inputs.target-platform }} Workloads | ||
shell: pwsh | ||
run: | | ||
dotnet tool install -g uno.check | ||
("${{ inputs.target-platform }} ".Split(' ') | ForEach-Object { | ||
$target = $_.Replace("_win", "").Replace("_macos", "") | ||
if (![string]::IsNullOrEmpty($target)) { | ||
echo "target: $target" | ||
uno-check -v --ci --non-interactive --fix --target $target --skip vswin --skip vsmac --skip xcode --skip vswinworkloads --skip androidemulator --skip dotnetnewunotemplates | ||
echo "uno-check finished for target: $target " | ||
} | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We probably could avoid running uno-check in a loop by adding multiple --target
options instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean?
This is the standard behaviour of the mini-workflow step included in the Uno platform template.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah! That's right, then the other one probably should be changed as well, but that will do for now then.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few additional comments.
- name: Install ${{ inputs.target-platform }} Workloads | ||
shell: pwsh | ||
run: | | ||
dotnet tool install -g uno.check | ||
("${{ inputs.target-platform }} ".Split(' ') | ForEach-Object { | ||
$target = $_.Replace("_win", "").Replace("_macos", "") | ||
if (![string]::IsNullOrEmpty($target)) { | ||
echo "target: $target" | ||
uno-check -v --ci --non-interactive --fix --target $target --skip vswin --skip vsmac --skip xcode --skip vswinworkloads --skip androidemulator --skip dotnetnewunotemplates | ||
echo "uno-check finished for target: $target " | ||
} | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah! That's right, then the other one probably should be changed as well, but that will do for now then.
Co-authored-by: Jérôme Laban <[email protected]>
This PR implements an alternative way for consuming Uno.Check - from GitHub Actions.
This will appear in the GitHub Marketplace once a release on the repo is published or a tag is created.
This also removes the need for the massive unnecessary workflow files shipped with the Uno templates wizard downstream.