Is there any filter that if PR has e.g. README.md update or other files/folders (we could add to the filter later on) then this GitHub Action wouldn't be triggered?

For example this action https://github.com/stride3d/stride-website/blob/master/.github/workflows/stride-website-release-azure.yml has paths-ignore: where I listed files and folders I don't want to trigger the GitHub Action.

@VaclavElias I've added paths as suggested. Let me know what you think.

@xen2 there is one change that requires updating the jobs in TeamCity:

-<BuildProperties>Configuration=Release;NoWarn=1591;DeployExtension=false;StridePlatforms=$([MSBuild]::Escape('$(StridePlatforms)'));StrideGraphicsApiDependentBuildAll=$(StrideGraphicsApiDependentBuildAll)</BuildProperties>
+<BuildProperties>NoWarn=1591;DeployExtension=false;StridePlatforms=$([MSBuild]::Escape('$(StridePlatforms)'));StrideGraphicsApiDependentBuildAll=$(StrideGraphicsApiDependentBuildAll)</BuildProperties>

I have removed Configuration=Release in BuildProperties so that this parameter can be passed to the job. This means it needs to be added back to all jobs on TeamCity that require a Release build (esp. the ones doing the final packaging). It's ok to change them now: it won't have any effect when running on a branch that stills has the previous value of BuildProperties.

edit: I've changed my mind. The new build jobs will not use Stride.build at all, as that file was mainly created to simplify the process in TeamCity. Instead the actual msbuild and dotnet command lines will be used.

@VaclavElias @xen2 as far as I'm concerned the PR is ready. The only remaining task before merging is the configuration on the repository itself. Let me know when that part is done so I can merge.

I have updated action permissions (I checked each of them and ended up with same choices as yours).