Add one or more Github Actions to the this git repository.
Requirement Description
Start with adding an adapted version of a .NET starter workflow.
When adapting it, make sure that you are using a .NET version 7, the same that we told you to install on your local computers.
That workflow shall be executed on all pushes and merge of pull-requests in your repository.
Add a workflow that releases your chirp executable, i.e., a single file .NET application.
The workflow should build and test your project whenever you push a new version that is accordingly tagged (git tag) to your repository.
When all tests pass, create at least three executables of your Chirp! project, one for Windows, one for MacOS, and one for Linux (-x64).
If you want to, publish executables for ARM processors too.
Each executable shall be distributed as compressed with zip file.
All of the above steps shall be executed in an ubuntu-latest environment, i.e., you want to cross-compile for the different targets.
Since everybody in this course has .NET 7 installed it is sufficient to publish a platform-dependent single file application, i.e., not a self-contained application.
Hints:
Likely you can combine the building blocks from the lecture notes and the reading material into a working solution.
To publish a release of your project, you might want to use the softprops/action-gh-release action
You might use this blog post for inspiration on how to create releases for various operating systems. Note though, that you want to build in one environment (ubuntu-latest) instead of three as in the given example, i.e., you do not need a build matrix.
To allow a GitHub action to create releases, you have to grant it write access. You do that on GitHub in your repository under Settings → Actions → General under Workflow permissions enable "Read and write permissions", see the official documentation
Description
Add one or more Github Actions to the this git repository.
Requirement Description
Hints:
Likely you can combine the building blocks from the lecture notes and the reading material into a working solution. To publish a release of your project, you might want to use the softprops/action-gh-release action You might use this blog post for inspiration on how to create releases for various operating systems. Note though, that you want to build in one environment (ubuntu-latest) instead of three as in the given example, i.e., you do not need a build matrix. To allow a GitHub action to create releases, you have to grant it write access. You do that on GitHub in your repository under Settings → Actions → General under Workflow permissions enable "Read and write permissions", see the official documentation
Acceptence criteria
Resources