Always trigger CI/CD Workflow

[jonaswre]

If you want to enforce a successful build, you will need to set CI/CD Workflow to be required by the policy.

You will encounter some situations where no CI/CD Workflow is started, because no build is needed.
In that case you will need to override the policy.

I think it would be useful to start the CI/CD Workflow anyway and make it succeed immediately.

This adds more consistency in the process.
Currently you need to know the common delay between PRHandler and CI/CD Workflow. If it takes longer then "normal" you need to understand if its not needed or something is wrong.

[jonaswre]

@freddydk have you encountered this?

[jonaswre]

I traced the "issue"
It was a PR that only consisted of .md files.

AL-Go/Templates/AppSource App/.github/workflows/PullRequestHandler.yaml

Line 6 in f4f2edb

- '**.md'

why do you ignore them?

[freddydk]

The reason is really that there is nothing to build and it would just be a waste of resources - that's why I added the pattern back in the days.

[jonaswre]

I couldn't find anyway to exclude the rule if only md file are present. Which would be a solution but this might require changes from github.

Maybe the CICD Workflow could just decide if it needs to build.
That would increase the waste, but in relation to the whole build thats only small factor.

[freddydk]

Yeah, so always run the CI/CD, but complete quickly - sounds like the right thing to do

[jonaswre]

It would be good to be able to configure "complete quickly". Maybe there are other pattern that don't require a new build.