Skip to main content

Github–Create a new release–The automated version

Yesterday I showed you how to create a new release in Github manually. This was a good starting point as it introduced the different elements of a release and the options we have. Today let us automate the process of creating a release on GitHub using GitHub Actions.

Create a new release using Github Actions

  • Go to Actions inside Github and click on new workflow.

  • We’ll not use an existing template but instead choose to setup the workflow ourself:

  • Paste the following yaml content in the editor screen. I’ll explain it afterwards…


Explanation of the Workflow

  • name: This is the name of your workflow. You can name it something like "Release".

  • on: Specifies the event that will trigger the workflow. In this case, it’s triggered by a push to a tag that matches the pattern v*.*.* (e.g., v1.0.0).

  • jobs: This defines the job that will be run by the workflow.

  • runs-on: Specifies the environment where the job will run. In this case, it uses the latest Windows environment.

  • steps: This section lists the steps the job will take. I’ll focus on the actions specific for the release

    • actions/checkout@v4: Checks out the repository's code so that the workflow can access it.

    • actions/create-release@v1: This action is used to create the release. It uses the GITHUB_TOKEN secret to authenticate with GitHub. The release is named after the tag and includes a basic description. The draft and prerelease options can be set to true if you want the release to be a draft or a pre-release.

    • actions/upload-release-asset@v1: This action uploads assets (like compiled binaries, zipped files, etc.) to the release. The upload_url is provided by the previous step where the release was created.

Trigger the workflow

The workflow is set to trigger on a tag push that matches the pattern v*.*.*. Create a new tag and push it to trigger the workflow.

I can do this through the commandline:

git tag v1.0.0
git push origin v1.0.0

Or if you prefer a GUI, you can use for example Github Desktop:

  • Go to the History tab to see the latest commits: 

  • Right click on a commit and choose Create tag:
  • Specify a tag name using the v*.*.* pattern
  • Now we have one change that we should push to our remote origin:

The Github Actions workflow should pick up this change and start the release pipeline:

Once completed we have a brand new release available:


Nice!

Remark: We can further improve this by automatically generating the release notes but that is something I’ll leave for another post.




Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...