Closed ReenigneArcher closed 3 months ago
The .github/workflows/msbuild.yml
file has undergone significant enhancements to improve workflow efficiency and responsiveness. Key updates include the addition of triggers for pull requests, refined concurrency settings, and upgraded action versions. The script execution process has been improved for better readability, and environment variables have been integrated. These changes collectively enhance the workflowβs flexibility, maintainability, and reliability within the CI/CD pipeline.
Files | Change Summary |
---|---|
.github/.../msbuild.yml |
Added pull request trigger, updated concurrency settings, advanced action versions, refined scripts for readability, integrated environment variables, and upgraded artifact upload actions. |
In workflows where the code does flow,
Updates come with a gentle glow.
Concurrency now wisely tuned,
And scripts by better logic pruned.
Actions updated, artifacts soar,
Efficiency knocks on CIβs door. π
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
@TheElixZammuto this is working now. https://github.com/ReenigneArcher/moonlight-xbox/actions/runs/10231641854
After this is merged, I plan on working on a way to cache the third party builds as that part is quite time consuming (~25 minutes).
Looks like i need to tweak something else. I have it working in my repo, so should be close.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
I think I've fixed this.
Thank you as always!
This PR makes some changes the msbuild.yml workflow. I am happy to describe any changes in further detail if needed.
pull_request
allows you to verify if PRs have successful builds and/or download the artifacts for testing. This is limited to opened, synchronized (when new commits are pushed to the PR branch), and re-opened events.push
is limited to only themaster
branch.workflow_dispatch
allows you to run this workflow manually if you ever need to check the build state.concurrency
changes will ensure only a single workflow will run for each ref. This means if a PR contributor pushes new changes to their branch, it will cancel the in process workflow and trigger a new run.env
section was shortened, but equivalent to the previousshell: pwsh
as this is the default for Windows runnersworking-directory: ${{env.GITHUB_WORKSPACE}}
as this is the default for all job stepsThere is a repository setting to configure how github workflows run from outside collaborators. The options are:
No matter which option you select, PRs from forks will never have access to secrets. There are none in your workflow currently, so this is just FYI.
P.S. In another PR, I would like to add dependabot to help you keep actions and git submodules updated automatically. Unfortunately, it does not have support for vcpkg (see: https://github.com/dependabot/dependabot-core/issues/2027)
Summary by CodeRabbit
New Features
Improvements