CI: update to pyansys/actions@v3

[jorgepiloto]

The latest patch for pyansys/actions@v3 should fix the issues that we faced in #60. This pull-request reverts the changes to verify this new version solved the issue.

Fixes #59.

[nikitadpopel]

Hey! Just wondering what this does out of curiosity 😄 And how just updating the version in this .github/workflows/ci_cd.yml will cause the runner to use other version. Does the runner read in this yaml in the beginning of the run every time to set up all its configs?

[jorgepiloto]

Hi @nikitadpopel, let me answer your question.

All the YML files inside the special directory .github/workflows are assumed to be CI/CD configuration files. Dependending on their configuration, those are executed on particular events like push or merge.

Both default CI/CD machine by GitHub or a self-hosted runner read YML files as soon as you push changes.

Since the YML files for CI/CD can get a bit extensive, GitHub introduced the so-called "reusable workflows". The idea is that developers can write small and common pieces of workflows so those can be reused across other repositories.

Hence, we created pyansys/actions. This repository has various directories containing a single YML file. These files accepts inputs so you can customize the logic according to their values.

The syntax to use one of this "reusable workflows" is as follows:

uses: <organization>/<repository>/<directory>@version

Some months ago, we updated PyAnsys actions from v2 to v3. We just carried a bug fix in v3 related to the deployment of development documentation. This pull-request allows us to benefit from such patch release.

[nikitadpopel]

Hi @nikitadpopel, let me answer your question.

All the YML files inside the special directory .github/workflows are assumed to be CI/CD configuration files. Dependending on their configuration, those are executed on particular events like push or merge.

Both default CI/CD machine by GitHub or a self-hosted runner read YML files as soon as you push changes.

Since the YML files for CI/CD can get a bit extensive, GitHub introduced the so-called "reusable workflows". The idea is that developers can write small and common pieces of workflows so those can be reused across other repositories.

Hence, we created pyansys/actions. This repository has various directories containing a single YML file. These files accepts inputs so you can customize the logic according to their values.

The syntax to use one of this "reusable workflows" is as follows:

uses: <organization>/<repository>/<directory>@version

Some months ago, we updated PyAnsys actions from v2 to v3. We just carried a bug fix in v3 related to the deployment of development documentation. This pull-request allows us to benefit from such patch release.

Thanks for clarifying!